Medical imaging, efficient sharing and secure handling of medical imaging information

ABSTRACT

An MRI image processing and analysis system may identify instances of structure in MRI flow data, e.g., coherency, derive contours and/or clinical markers based on the identified structures. The system may be remotely located from one or more MRI acquisition systems, and perform: error detection and/or correction on MRI data sets; segmentation; visualization of flow superimposed on anatomical structure, quantification; verification; and/or generation of patient specific 4-D flow protocols. A protected health information (PHI) service is provided which de-identifies medical study data and allows medical providers to control PHI data, and uploads the de-identified data to an analytics service provider (ASP) system. A web application is provided which merges the PHI data with the de-identified data while keeping control of the PHI data with the medical provider. A Trusted Broker Service (TBS) is integrated with the PHI service pipeline and allows an authorized third party to control access to data that has been uploaded to the ASP from an authorized uploader.

BACKGROUND Technical Field

The present disclosure generally relates to magnetic resonance imaging (MRI), for instance four-dimensional (4-D) flow MRI, and the sharing of medical imaging and other information over communications networks or channels.

Description of the Related Art

MRI is most commonly employed in medical imaging, although can be used in other fields. MRI machines include a main magnet which is typically an annular array of coils having a central or longitudinal bore. The main magnet is capable of producing a strong stable magnetic field (e.g., 0.5 Tesla to 3.0 Tesla). The bore is sized to receive at least a portion of an object to be imaged, for instance a human body. When used in medical imaging applications, the MRI machine may include a patient table which allows a prone patient to be easily slid or rolled into and out of the bore.

MRI machines also include gradient magnets. The gradient magnets produce a variable magnetic field that is relatively smaller than that produced by the main magnet (e.g., 180 Gauss to 270 Gauss), allowing selected portions of an object (e.g., patient) to be imaged. MRI machines also include radio frequency (RF) coils which are operated to apply radiofrequency energy to selected portions of the object (e.g., patient) to be imaged. Different RF coils may be used for imaging different structures (e.g., anatomic structures). For example, one set of RF coils may be appropriate for imaging a neck of a patient, while another set of RF coils may be appropriate for imaging a chest or heart of the patient. MRI machines commonly include additional magnets, for example resistive magnets and/or permanent magnets.

The MRI machine typically includes, or is communicatively coupled to a computer system used to control the magnets and/or coils and/or to perform image processing to produce images of the portions of the object being imaged. Conventionally, MRI machines produce magnitude data sets which represent physical structures, for instance anatomical structures. The data sets often conform to the Digital Imaging and Communications in Medicine (DICOM) standard. DICOM files typically include pixel data and metadata in a prescribed format.

BRIEF SUMMARY

A method of operating a medical analytics platform, the medical analytics platform including an analytics service provider (ASP) system may be summarized as including receiving, by at least one processor of the ASP system, medical study data along with a unique identifier of the medical study data; storing, by at least one processor of the ASP system, the unique identifier of the medical study data on the ASP system; sending, by at least one processor of the ASP system, a request for access instructions for the received medical study data, wherein the request includes the unique identifier of the medical study data; receiving, by at least one processor of the ASP system, the access instructions in response to the request; and storing, by at least one processor of the ASP system, the medical study data on the ASP system using the received access instructions. The access instructions may include encryption information for encrypting the medical study data and the storing the medical study data may include encrypting the medical study data for storage using the encryption information. The access instructions may include a pre-signed, time-expiring access uniform resource locator (URL) and the storing the medical study data may include storing the medical study data to the pre-signed, time-expiring access URL according to an access policy associated with the pre-signed, time-expiring access URL.

The method may further include receiving, by at least one processor of the ASP system, a request from a client processor-based device for the medical study data stored on the ASP system; retrieving, by at least one processor of the ASP system, the identifier of the medical study data from storage on the ASP system in response to receiving the request for the medical study data stored on the ASP system; sending, by at least one processor of the ASP system, a request for access instructions for the medical study data stored on the ASP system, wherein the request for access instructions includes the unique identifier of the medical study data; receiving, by at least one processor of the ASP system, the access instructions in response to the request for the access instructions; accessing, by at least one processor of the ASP system, the medical study data stored on the ASP system using the received access instructions; and sending, by at least one processor of the ASP system, the accessed medical study data stored on the ASP system to the client processor-based device in response to the request received from the client processor-based device. The access instructions may include decryption information for decrypting the medical study data and the accessing the medical study data may include decrypting the medical study data using the decryption information.

The method may further include retrieving from storage on the ASP system, by at least one processor of the ASP system, a file name associated with the medical study data stored on the ASP system in response to receiving the request for the medical study data stored on the ASP system, wherein the access instructions include a pre-signed download uniform resource locator (URL) and wherein the accessing the medical study data includes requesting, by at least one processor of the ASP system, the medical study data at a location specified by the pre-signed download uniform URL. The medical study data may be received along with the unique identifier of the medical study data from a medical study data uploader (MSDU) system, the request for access instructions for the received medical study data may be sent to a trusted broker service (TBS) system, and the access instructions may be received from the TBS system in response to the request.

The method may further include before the receiving the medical study data along with the unique identifier of the medical study data: receiving, by at least one processor of the ASP system, a request from the MSDU system for an authentication token and an address of the trusted broker service (TBS) system, the request including an application programming interface (API) key and unique secret stored on the MSDU system; authenticating, by at least one processor of the ASP system, the request from the MSDU system using the application programming interface (API) key and the unique secret; sending, by at least one processor of the ASP system, the authentication token and the address of the TBS system to the MSDU system based on authentication of the request from the MSDU system; receiving, by at least one processor of the ASP system, a request from the TBS system for verification of the authentication token; verifying, by at least one processor of the ASP system, the authentication token in response to the request for verification from the TBS system; and sending, by at least one processor of the ASP system, verification of the authentication token to the TBS system. The MSDU system may be part of a protected health information (PHI) system. The medical study data may be de-identified medical study data that is de-identified by the PHI system.

A method of operating a medical analytics platform, the medical analytics platform including a trusted broker service (TBS) system may be summarized as including receiving, by at least one processor of the TBS system, a request from an analytics service provider (ASP) system for access instructions for medical study data to be stored on the ASP system, wherein the request includes a unique identifier of the medical study data; retrieving, by at least one processor of the TBS system, access instructions for the medical study data using the unique identifier; and sending, by at least one processor of the TBS system, the access instructions for the medical study data to the ASP system in response to the request for the access instructions. The access instructions may include encryption information for encrypting the medical study data by the ASP system for storage on the ASP system. The access instructions may include a pre-signed, time-expiring access uniform resource locator (URL) to which the medical study data is to be stored by the ASP system.

The method may further include before the receiving the request from the ASP system for access instructions for the medical study data: receiving, by at least one processor of the TBS system, metadata regarding the medical study data along with an authentication token from medical study data uploader (MSDU) system; sending, by at least one processor of the TBS system, a request to the ASP system for verification of the authentication token; receiving, by at least one processor of the TBS system, verification of the authentication token from the ASP system in response to the request for verification of the authentication token; and in response to the verification of the authentication token: generating, by at least one processor of the TBS system, the unique identifier of the medical study data; generating, by at least one processor of the TBS system, the access information for the medical study data; associating, by at least one processor of the TBS system, the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; storing on the TBS system, by at least one processor of the TBS system, the metadata regarding the medical study data; storing on the TBS system, by at least one processor of the TBS system, the association of the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; and sending, by at least one processor of the TBS system, the unique identifier of the medical study data to the MSDU system. The MSDU system may be part of a protected health information (PHI) system. The medical study data may be de-identified medical study data that is de-identified by the PHI system.

The method may be summarized as including receiving, by at least one processor of the TBS system, a request to revoke access to the medical study data stored on the ASP system; locating, by at least one processor of the TBS system, metadata stored on the TBS system regarding the medical study data stored on the ASP system for which access is to be revoked; removing from the TBS system, by at least one processor of the TBS system, one or more of: the metadata regarding the medical study data, the access information for the medical study data, and the unique identifier of the medical study data. The request to revoke access to the medical study data stored on the ASP system may be received from an authorized client processor-based device. The request to revoke access to the medical study data stored on the ASP system may be received from a PHI system.

A method of operating a medical analytics platform, the medical analytics platform including a medical study data uploader (MSDU) system may be summarized as including sending, by at least one processor of the MSDU system, a request to an analytics service provider (ASP) system for an authentication token and an address of a trusted broker service (TBS) system, the request including an application programming interface (API) key and unique secret stored on the MSDU system; receiving from the ASP system, by at least one processor of the MSDU system, the authentication token and the address of the TBS system in response to the request sent to the ASP system; sending, by at least one processor of the MSDU system, metadata regarding medical study data along with the authentication token to the TBS system using the address of the TBS system; receiving from the TBS system, by at least one processor of the MSDU system, a unique identifier of the medical study data in response to the sending of the metadata regarding medical study data along with the authentication token to the TBS system; and sending to the ASP system, by at least one processor of the MSDU system, the unique identifier of the medical study data along with the medical study data for storage on the ASP system. The MSDU system may be part of a protected health information (PHI) system. The medical study data may be de-identified medical study data that is de-identified by the PHI system.

A method of operating a medical analytics platform, the medical analytics platform including a medical study data uploader (MSDU) system, an analytics service provider (ASP) system and a trusted broker service (TBS) system, may be summarized as including sending, by at least one processor of the MSDU system, metadata regarding medical study data to the TBS system; generating, by at least one processor of the TBS system, a unique identifier of the medical study data; generating, by at least one processor of the TBS system, access information for the medical study data; associating, by at least one processor of the TBS system, the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; storing on the TBS system, by at least one processor of the TBS system, the metadata regarding the medical study data; storing on the TBS system, by at least one processor of the TBS system, the association of the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; sending, by at least one processor of the TBS system, the unique identifier of the medical study data to the MSDU system; sending to the ASP system, by at least one processor of the MSDU system, the unique identifier of the medical study data along with the medical study data for storage on the ASP system; storing, by at least one processor of the ASP system, the unique identifier of the medical study data on the ASP system; sending, by at least one processor of the ASP system, a request for access instructions for the received medical study data, wherein the request includes the unique identifier of the medical study data; receiving, by at least one processor of the ASP system, the access instructions in response to the request; and storing, by at least one processor of the ASP system, the medical study data on the ASP system using the received access instructions.

The method may further include before the sending the metadata regarding medical study data to the TBS system: sending, by at least one processor of the MSDU system, a request to the ASP system for an authentication token and an address of the TBS system, the request including an application programming interface (API) key and unique secret stored on the MSDU system; receiving from the ASP system, by at least one processor of the MSDU system, the authentication token and an address of the TBS system, wherein the sending the metadata regarding medical study data to the TBS system includes sending, by at least one processor of the MSDU system, the metadata regarding the medical study data along with the authentication token to the TBS system using the address of the TBS system; sending, by at least one processor of the TBS system, a request to the ASP system for verification of the authentication token in response to receiving the authentication token from the MSDU system; verifying, by at least one processor of the ASP system, the authentication token in response to the request for verification from the TBS system; and sending, by at least one processor of the ASP system, verification of the authentication token to the TBS system, wherein the generating the unique identifier of the medical study data, the generating the access information for the medical study data, the associating the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data, and the storing on the TBS system the metadata regarding the medical study data are all dependent on the verification of the authentication token in response to receiving the authentication token from the MSDU system.

The method may further include removing from the TBS system, by at least one processor of the TBS system, one or more of: the metadata regarding the medical study data, the access information for the medical study data, and the unique identifier of the medical study data in order to revoke access to the medical study data stored on the APS system. The access instructions may include encryption information for encrypting the medical study data by the ASP system for storage on the ASP system. The access instructions may include a pre-signed, time-expiring access uniform resource locator (URL) to which the medical study data is to be stored by the ASP system. The MSDU system may be part of a protected health information (PHI) system.

An analytics service provider (ASP) system of a medical analytics platform, the medical analytics platform comprising the ASP system, a medical study data uploader (MSDU) system and a trusted broker service (TBS) system, may be summarized as including at least one nontransitory processor-readable storage medium that stores at least one of processor-executable instructions or data; and at least one processor communicably coupled to the at least one nontransitory processor-readable storage medium, in operation the at least one processor: receives medical study data along with a unique identifier of the medical study data; stores the unique identifier of the medical study data on the ASP system; sends a request for access instructions for the received medical study data, wherein the request includes the unique identifier of the medical study data; receives the access instructions in response to the request; and stores the medical study data on the ASP system using the received access instructions. The MSDU system may be part of a protected health information (PHI) system. The medical study data may be de-identified medical study data that is de-identified by the PHI system.

A trusted broker service (TBS) system of a medical analytics platform, the medical analytics platform comprising the TBS system, an analytics service provider (ASP) system a medical study data uploader (MSDU) system, may be summarized as including at least one nontransitory processor-readable storage medium that stores at least one of processor-executable instructions or data; and at least one processor communicably coupled to the at least one nontransitory processor-readable storage medium, in operation the at least one processor: receives a request from the ASP system for access instructions for medical study data to be stored on the ASP system, wherein the request includes a unique identifier of the medical study data; retrieves access instructions for the medical study data using the unique identifier; and sends the access instructions for the medical study data to the ASP system in response to the request for the access instructions.

In operation, the at least one processor may, before the at least one processor receives the request from the ASP system for access instructions for the medical study data: receive metadata regarding the medical study data along with an authentication token from the MSDU system; send a request to the ASP system for verification of the authentication token; receive verification of the authentication token from the ASP system in response to the request for verification of the authentication token; and in response to the verification of the authentication token: generate the unique identifier of the medical study data; generate the access information for the medical study data; associate the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; store on the TBS system the metadata regarding the medical study data; store on the TBS system the association of the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; and send the unique identifier of the medical study data to the MSDU system. The MSDU system may be part of a protected health information (PHI) system. The access instructions may include encryption information for encrypting the medical study data by the ASP system for storage on the ASP system. The access instructions may include a pre-signed, time-expiring access uniform resource locator (URL) to which the medical study data is to be stored by the ASP system.

A method of operating an analytics platform, the analytics platform including a data uploader (DU) system, an analytics service provider (ASP) system and a trusted broker service (TBS) system, may be summarized as including sending to the TBS system, by at least one processor of the DU system, metadata regarding data; generating, by at least one processor of the TBS system, a unique identifier of the data; generating, by at least one processor of the TBS system, access information for the data; associating, by at least one processor of the TBS system, the unique identifier of the data with the access information for the data and the metadata regarding the data; storing on the TBS system, by at least one processor of the TBS system, the metadata regarding the data; storing on the TBS system, by at least one processor of the TBS system, the association of the unique identifier of the data with the access information for the data and the metadata regarding the data; sending, by at least one processor of the TBS system, the unique identifier of the data to the DU system; sending to the ASP system, by at least one processor of the DU system, the unique identifier of the data along with the data for storage on the ASP system; storing, by at least one processor of the ASP system, the unique identifier of the data on the ASP system; sending, by at least one processor of the ASP system, a request for access instructions for the received data, wherein the request includes the unique identifier of the data; receiving, by at least one processor of the ASP system, the access instructions in response to the request; and storing, by at least one processor of the ASP system, the data on the ASP system using the received access instructions.

A method of operating a medical analytics platform, the medical analytics platform including an analytics service provider (ASP) system and a protected health information (PHI) system, the method may be summarized as including: storing, by at least one processor of the ASP system, de-identified medical study data on at least one nontransitory processor-readable storage medium of the ASP system; storing, by at least one processor of the PHI system, PHI data associated with the de-identified medical study data on at least one nontransitory processor-readable storage medium of the PHI system; sending, by the at least one processor of the PHI system, PHI data for a requested medical study to a client processor-based device over at least one communications network; and sending, by the at least one processor of the ASP system, de-identified medical study data for the requested medical study to the client processor-based device over the at least one communications network.

The PHI system may be communicatively coupled to a private network, the method may further include: verifying, by the at least one processor of the ASP system or the at least one processor of the PHI system, that the client processor-based device has access to the private network. The method may further include: receiving, by the at least one processor of the ASP system, a request for a PHI access token from the client processor-based device over the at least one communications network; sending, by the at least one processor of the ASP system, an encrypted PHI access token to the client processor-based device over the at least one communications network; receiving, by the at least one processor of the PHI system, a request for PHI data for the medical study from the client processor-based device, the request including the encrypted PHI access token; sending, by the at least one processor of the PHI system, the encrypted PHI access token to the ASP system over the at least one communications network; validating, by the at least one processor of the ASP system, the received encrypted PHI access token; and notifying, by the at least one processor of the ASP system, the PHI system that the PHI access token is valid, wherein sending the requested PHI data to the client processor-based device may be responsive to the at least one processor of the PHI system receiving the validation notification from the ASP system. The method may further include: receiving, by the at least one processor of the PHI system, medical study data which includes PHI data; removing, by the at least one processor of the PHI system, the PHI data from the medical study data to generate de-identified medical study data; storing, by the at least one processor of the PHI system, the PHI data in the at least one nontransitory processor-readable storage medium of the PHI system; and sending, by the at least one processor of the PHI system, the de-identified medical study data to the ASP system over the at least one communications network. Receiving medical study data which includes PHI data may include receiving medical imaging data from a scanner. Sending the de-identified medical study data to the ASP system may include sending the de-identified medical study data to the ASP system using a representational state transfer (REST) application programming interface. Removing the PHI data from the medical study data may include: removing, by the at least one processor of the PHI system, fields which are allowed to be deleted; and replacing, by the at least one processor of the PHI system, data in fields which are not allowed to be deleted with obfuscated replacement data. The method may further include: associating, by the at least one processor of the PHI system, a unique identifier with the medical study data for a medical study; storing, by the at least one processor of the PHI system, the unique identifier in the at least one nontransitory processor-readable storage medium of the PHI system; and sending, by the at least one processor of the PHI system, the unique identifier with the de-identified medical data for the medical study to the ASP system over the at least one communications network. The method may further include: receiving, by at least one processor of the client processor-based device, the PHI data from the PHI system over the at least one communications network; receiving, by the at least one processor of the client processor-based device, the de-identified medical study data from the ASP system over the at least one communications network; merging, by the at least one processor of the client processor-based device, the PHI data and the de-identified medical study data to generate re-identified medical study data; and presenting, by the at least one processor of the client processor-based device, the re-identified medical study data to a user of the client processor-based device. The method may further include: generating, by the at least one processor of the ASP system, analytics data relating to the de-identified medical study data; and sending, by the at least one processor of the ASP system, the generated analytics data to the PHI system over the at least one communications network. The method may further include: receiving, by the at least one processor of the ASP system, a request to generate analytics data from the client processor-based device over the at least one communications network, wherein generating the analytics data may be responsive to receiving the request to generate analytics data from the client processor-based device. Generating analytics data may include generating at least one of a report or a secondary capture object, and sending the generated analytics data to the PHI system may include sending the at least one of the report or the secondary capture object to the PHI system over the at least one communications network for storage on the at least one nontransitory processor-readable storage medium communicatively coupled with the PHI system. The method may further include: providing, by the at least one processor of the PHI system, a list of available studies to the client processor-based device over the at least one communications network; and receiving, by the at least one processor of the PHI system, a selection of at least one of the available studies in the list from the client processor-based device over the at least one communications network. The method may further include: periodically sending, by the at least one processor of the PHI system, a check for updates to the ASP system over the at least one communications network; determining, by the at least one processor of the ASP system, whether any updates to the PHI system are needed; and responsive to determining that at least one update of the PHI system is needed, sending, by the at least one processor of the ASP, update data to the PHI system over the at least one communications network.

A method of operating an analytics service provider (ASP) system of a medical analytics platform, the medical analytics platform including the ASP system and a protected health information (PHI) system, the PHI system storing PHI data associated with de-identified medical study data on at least one nontransitory processor-readable storage medium of the PHI system, the method may be summarized as including: storing, by at least one processor of the ASP system, the de-identified medical study data on at least one nontransitory processor-readable storage medium of the ASP system; and sending, by the at least one processor of the ASP system, de-identified medical study data for a requested medical study to a client processor-based device over at least one communications network to be merged by the client processor-based device with PHI data received by the client processor-based device from the PHI system over the at least one communications network.

The method may further include: receiving, by the at least one processor of the ASP system, a request for a PHI access token from the client processor-based device over the at least one communications network; sending, by the at least one processor of the ASP system, an encrypted PHI access token to the client processor-based device over the at least one communications network; receiving, by the at least one processor of the ASP system, the encrypted PHI access token from the PHI system over the at least one communications network; validating, by the at least one processor of the ASP system, the received encrypted PHI access token; and notifying, by the at least one processor of the ASP system, the PHI system that the PHI access token is valid. The method may further include: receiving, by the at least one processor of the ASP system, the de-identified medical study data from the PHI system over the at least one communications network. The method may further include: generating, by the at least one processor of the ASP system, analytics data relating to the de-identified medical study data; and sending, by the at least one processor of the ASP system, the generated analytics data to the PHI system over the at least one communications network. The method may further include: receiving, by the at least one processor of the ASP system, a request to generate analytics data from the client processor-based device over the at least one communications network, wherein generating the analytics data may be responsive to receiving the request to generate analytics data from the client processor-based device. Generating analytics data may include generating at least one of a report or a secondary capture object, and sending the generated analytics data to the PHI system may include sending the at least one of the report or the secondary capture object to the PHI system over the at least one communications network for storage on the at least one nontransitory processor-readable storage medium communicatively coupled with the PHI system. The method may further include: periodically receiving, by the at least one processor of the ASP system, a check for updates from the PHI system over the at least one communications network; determining, by the at least one processor of the ASP system, whether any updates to the PHI system are needed; and responsive to determining that at least one update of the PHI system is needed, sending, by the at least one processor of the ASP, update data to the PHI system over the at least one communications network. The method may further include: receiving, by at least one processor of the client processor-based device, the PHI data from the PHI system over the at least one communications network; receiving, by the at least one processor of the client processor-based device, the de-identified medical study data from the ASP system over the at least one communications network; merging, by the at least one processor of the client processor-based device, the PHI data and the de-identified medical study data to generate re-identified medical study data; and presenting, by the at least one processor of the client processor-based device, the re-identified medical study data to a user of the client processor-based device.

An analytics service provider (ASP) system of a medical analytics platform, the medical analytics platform including the ASP system and a protected health information (PHI) system, the PHI system stores PHI data associated with de-identified medical study data on at least one nontransitory processor-readable storage medium of the PHI system, the ASP system may be summarized as including: at least one nontransitory processor-readable storage medium that stores at least one of processor-executable instructions or data; and at least one processor communicably coupled to the at least one nontransitory processor-readable storage medium, in operation the at least one processor: stores the de-identified medical study data on the at least one nontransitory processor-readable storage medium; and sends de-identified medical study data for a requested medical study to a client processor-based device over at least one communications network to be merged by the client processor-based device with PHI data received by the client processor-based device from the PHI system over the at least one communications network.

The at least one processor may: receive a request for a PHI access token from the client processor-based device over at least one communications network; send an encrypted PHI access token to the client processor-based device over the at least one communications network; receive the encrypted PHI access token from the PHI system over the at least one communications network; validate the received encrypted PHI access token; and notify the PHI system that the PHI access token is valid over the at least one communications network. The at least one processor may: receive the de-identified medical study data from the PHI system over the at least one communications network. The at least one processor may: generate analytics data relating to the de-identified medical study data; and send the generated analytics data to the PHI system over the at least one communications network. The at least one processor may: receive a request to generate analytics data from the client processor-based device over the at least one communications network, wherein the at least one processor may generate the analytics data responsive to receipt of the request to generate analytics data from the client processor-based device. The analytics data may include at least one of a report or a secondary capture object, and the at least one processor may: send the at least one of the report or the secondary capture object to the PHI system over the at least one communications network for storage on at least one nontransitory processor-readable storage medium communicatively coupled with the PHI system. The at least one processor may: periodically receive a check for updates from the PHI system over the at least one communications network; determine whether any updates to the PHI system are needed; and responsive to a determination that at least one update of the PHI system is needed, send update data to the PHI system over the at least one communications network.

A method of operating a protected health information (PHI) system of a medical analytics platform, the medical analytics platform including the PHI system and an analytics service provider (ASP) system, the ASP system storing de-identified medical study data on at least one nontransitory processor-readable storage medium of the ASP system, the method may be summarized as including: storing, by at least one processor of the PHI system, PHI data associated with the de-identified medical study data on at least one nontransitory processor-readable storage medium of the PHI system; and sending, by the at least one processor of the PHI system, PHI data for a requested medical study to a client processor-based device over at least one communications network to be merged by the client processor-based device with de-identified medical study data received by the client processor-based device from the ASP system over the at least one communications network.

The method may further include: receiving, by the at least one processor of the PHI system, a request for PHI data for the medical study from a client processor-based device, the request including an encrypted PHI access token; sending, by the at least one processor of the PHI system, the encrypted PHI access token to the ASP system over the at least one communications network for validation; and receiving, by the at least one processor of the PHI system, a notification from the ASP system that the PHI access token is valid. The method may further include: receiving, by the at least one processor of the PHI system, medical study data which includes PHI data; removing, by the at least one processor of the PHI system, the PHI data from the medical study data to generate de-identified medical study data; storing, by the at least one processor of the PHI system, the PHI data in the at least one nontransitory processor-readable storage medium of the PHI system; and sending, by the at least one processor of the PHI system, the de-identified medical study data to the ASP system over the at least one communications network. Receiving medical study data which includes PHI data may include receiving medical imaging data from a scanner. Sending the de-identified medical study data to the ASP system may include sending the de-identified medical study data to the ASP system using a representational state transfer (REST) application programming interface. Removing the PHI data from the medical study data may include: removing, by the at least one processor of the PHI system, fields which are allowed to be deleted; and replacing, by the at least one processor of the PHI system, data in fields which are not allowed to be deleted with obfuscated replacement data. The method may further include: associating, by the at least one processor of the PHI system, a unique identifier with the medical study data for a medical study; storing, by the at least one processor of the PHI system, the unique identifier in the at least one nontransitory processor-readable storage medium of the PHI system; and sending, by the at least one processor of the PHI system, the unique identifier with the de-identified medical data for the medical study to the ASP system over the at least one communications network. The method may further include: receiving, by the at least one processor of the PHI system, analytics data relating to the de-identified medical study data from the ASP system over the at least one communications network; and storing, by the at least one processor of the PHI system, the received analytics data on at least one nontransitory processor-readable storage medium communicatively coupled with the PHI system. The method may further include: providing, by the at least one processor of the PHI system, a list of available studies to the client processor-based device over the at least one communications network; and receiving, by the at least one processor of the PHI system, a selection of at least one of the available studies in the list from the client processor-based device over the at least one communications network. The method may further include: periodically sending, by the at least one processor of the PHI system, a check for updates to the ASP system over the at least one communications network; and receiving, by the at least one processor of the PHI system, update data from the ASP system over the at least one communications network. The method may further include: receiving, by at least one processor of the client processor-based device, the PHI data from the PHI system over the at least one communications network; receiving, by the at least one processor of the client processor-based device, the de-identified medical study data from the ASP system over the at least one communications network; merging, by the at least one processor of the client processor-based device, the PHI data and the de-identified medical study data to generate re-identified medical study data; and presenting, by the at least one processor of the client processor-based device, the re-identified medical study data to a user of the client processor-based device.

A protected health information (PHI) system of a medical analytics platform, the medical analytics platform including the PHI system and an analytics service provider (ASP) system, the ASP system storing de-identified medical study data on at least one nontransitory processor-readable storage medium of the ASP system, the PHI system may be summarized as including: at least one nontransitory processor-readable storage medium that stores at least one of processor-executable instructions or data; and at least one processor communicably coupled to the at least one nontransitory processor-readable storage medium, in operation the at least one processor: stores PHI data associated with the de-identified medical study data on at least one nontransitory processor-readable storage medium of the PHI system; and sends PHI data for a requested medical study to a client processor-based device over at least one communications network to be merged by the client processor-based device with de-identified medical study data received by the client processor-based device from the ASP system over the at least one communications network.

The at least one processor may: receive a request for PHI data for the medical study from a client processor-based device, the request including an encrypted PHI access token; send the encrypted PHI access token to the ASP system over the at least one communications network for validation; and receive a notification from the ASP system that the PHI access token is valid. The at least one processor may: receive medical study data which includes PHI data; remove the PHI data from the medical study data to generate de-identified medical study data; store the PHI data in the at least one nontransitory processor-readable storage medium of the PHI system; and send the de-identified medical study data to the ASP system over the at least one communications network. The medical study data may include medical imaging data from a scanner. The at least one processor may send de-identified medical study data to the ASP system using a representational state transfer (REST) application programming interface. The at least one processor may: remove fields of the medical study data which are allowed to be deleted; and replace data in fields of the medical study data which are not allowed to be deleted with obfuscated replacement data. The at least one processor may: associate a unique identifier with the medical study data for a medical study; store the unique identifier in the at least one nontransitory processor-readable storage medium of the PHI system; and send the unique identifier with the de-identified medical data for the medical study to the ASP system over the at least one communications network. The at least one processor may: receive analytics data relating to the de-identified medical study data from the ASP system over the at least one communications network; and store the received analytics data on at least one nontransitory processor-readable storage medium communicatively coupled with the PHI system. The at least one processor may: provide a list of available studies to the client processor-based device over the at least one communications network; and receive a selection of at least one of the available studies in the list from the client processor-based device over the at least one communications network. The at least one processor may: periodically send a check for updates to the ASP system over the at least one communications network; and receive update data from the ASP system over the at least one communications network.

A method of querying and retrieving supplemental data for a medical scan may be summarized as including: receiving, by a protected health information (PHI) server, a request to retrieve supplemental data from a remote data storage, the request including at least: connection information that indicates information usable by the PHI server to connect to the remote data storage; identification information that indicates information usable by the PHI server to identify the supplemental data; and action information that indicates an action to perform on the requested supplemental data; querying, by the PHI server, the remote data storage based at least in part on the received connection information and identification information; retrieving, by the PHI server, the supplemental data based on the results of the querying of the remote data storage; and performing, by the PHI server, an action on the supplemental data based at least in part on the action information included in the request.

Receiving a request to retrieve supplemental data may include receiving a request that includes identification information, the identification information including one or more of: a related hash that identifies related scans, one or more tags usable for filtering the request, or data information. Receiving a request to retrieve supplemental data may include receiving a request that includes action information, the action information indicating one or more of a query only action, a process action, or a render action. The action information may include a query only action, and performing an action on the supplemental data may include returning results data without retrieving image data associated with the medical scan. The action information may include a process action, and performing an action on the supplemental data may include: de-identifying the retrieved supplemental data; storing the protected health information data on at least one nontransitory processor-readable storage medium; and sending the de-identified supplemental data to a remote server for processing. The action information may include a render action, and performing an action on the supplemental data may include: extracting image data from the retrieved supplemental data; and returning results data without storing the protected health information data. Receiving a request to retrieve supplemental data may include receiving a request to retrieve supplemental data from a web client via a web API on the PHI server. Receiving a request to retrieve supplemental data may include polling a remote server for unprocessed requests to retrieve supplemental data. The method may further include: determining, by the PHI server, that the remote data storage does not provide an API to fully filter the supplemental data as indicated in the request; and filtering, by the PHI server, the supplemental data according to the identifying information provided in the request.

A method of enriching worklist data stored on a protected health information (PHI) server may be summarized as including: long polling, by the PHI server, a remote server for changes to worklist data; receiving, by the PHI server, changed worklist data from the remote server, the changed worklist data including worklist data that has changed since a last synchronization date; and storing, by the PHI server, the changed worklist data on at least one nontransitory processor-readable storage medium.

Long polling a remote server for changes to worklist data may include establishing, by the PHI server, a connection with the remote server that indicates the last synchronization date. The method may further include: subsequent to receiving changed worklist data from the remote server, establishing a new connection with the remote server, the new connection indicating a new last synchronization date. The method may further include: sharing, by the PHI server, the changed worklist data with one or more users of an organization with which the PHI server is associated. The changed worklist data may include tag information, and sharing the changed worklist data with one or more users may include sharing the tag information with a plurality of users of the organization. The changed worklist data may include at least one of bookmark information associated with a particular user or new/viewed state information associated with a particular user, and sharing the changed worklist data with one or more users may include sharing the changed worklist data with the particular user associated with the bookmark information or the new/viewed state information. Receiving changed worklist data may include receiving changed worklist data associated with at least one of a user initiated event or a server initiated event. Receiving changed worklist data may include receiving changed worklist data associated with a user initiated event, the user initiated event including a user loading a scan, a user deleting an uploaded scan, a user adding, modifying, or deleting bookmark information, or a user adding, modifying, or deleting tag information. Receiving changed worklist data may include receiving changed worklist data associated with a server initiated event, the server initiated event including processing of an uploaded scan to generate a new entry. The method may further include: providing, by the PHI server, updated worklist data to a web application operated by a user of an organization with which the PHI server is associated, the updated worklist data including the changed worklist data.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

In the drawings, identical reference numbers identify similar elements or acts. The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements and angles are not necessarily drawn to scale, and some of these elements may be arbitrarily enlarged and positioned to improve drawing legibility. Further, the particular shapes of the elements as drawn, are not necessarily intended to convey any information regarding the actual shape of the particular elements, and may have been solely selected for ease of recognition in the drawings.

FIG. 1 is a schematic view of a networked environment including at least one MRI acquisition system and at least one image processing system, the MRI acquisition system located in a clinical setting and the image processing system located remotely from the MRI acquisition system and communicatively coupled therewith over one or more networks, according to one illustrated embodiment.

FIG. 2 is a functional block diagram of an MRI acquisition system and an MRI image processing and analysis system that provides MRI image processing and analysis services, according to one illustrated embodiment.

FIGS. 3A-3B are a flow diagram of an example push process executable by at least one processor, according to one illustrated embodiment.

FIGS. 4A-4B are a flow diagram of an example process of monitoring for artifacts and arching executable by at least one processor, according to one illustrated embodiment.

FIG. 5 is a schematic illustration of a PHI service pipeline, according to one illustrated embodiment.

FIG. 6 is a schematic illustration of a PHI service of FIG. 5, showing PHI data kept within a medical provider's network being merged with pixel data from an analytics service provider (ASP) system via the ASP's web application, according to one illustrated embodiment.

FIG. 7 is a schematic illustration of the PHI service of FIG. 5, showing DICOM files being stripped of PHI data, according to one illustrated embodiment.

FIG. 8 is a schematic illustration of the PHI service, showing a user operating a web application to request the ASP system to store a report on a registered PACS server of the user's organization, according to one illustrated embodiment.

FIG. 9 is a schematic illustration of the PHI service, showing how DICOM files are handled by the PHI server of the PHI service, according to one illustrated implementation.

FIG. 10 is a schematic illustration of the PHI service, showing how PHI service dependencies are organized, according to one illustrated embodiment.

FIGS. 11A-11B are system sequence diagrams illustrating a process for a launch sequence of the PHI service, according to one illustrated embodiment.

FIG. 12 is a flow diagram illustrating a process for implementing a de-identification service of the PHI service, according to one illustrated embodiment.

FIGS. 13A-13B are flow diagrams illustrating a process for a pusher or uploader service of the PHI service, according to one illustrated embodiment.

FIGS. 14A-14B are system sequence diagrams illustrating a process for web browser re-identification, according to one illustrated embodiment.

FIGS. 15A-15B are system sequence diagrams illustrating a process for implementing an artifact re-identification service, according to one illustrated embodiment.

FIG. 16 is a schematic illustration of a Trusted Broker Service (TBS) system integrated with the PHI service pipeline shown in FIG. 5, according to one illustrated embodiment.

FIG. 17 is a schematic illustration of the Uploader, ASP system and the TBS system showing how encryption based data uploads are performed by the TBS system, according to one illustrated embodiment.

FIG. 18 is a schematic illustration of an end user system, ASP system and the TBS system showing how encryption based data downloads are performed by the TBS system, according to one illustrated embodiment.

FIG. 19 is a schematic illustration of the Uploader, ASP system and the TBS system showing how access based data uploads are performed by the TBS system, according to one illustrated embodiment.

FIG. 20 is a schematic illustration of an end user system, ASP system and the TBS system showing how access based data downloads are performed by the TBS system, according to one illustrated embodiment.

FIG. 21 is a flow diagram illustrating a process operating an analytics service provider (ASP) system of a medical analytics platform, according to one illustrated embodiment.

FIG. 22 is a flow diagram illustrating a process of operating a trusted broker service (TBS) system of a medical analytics platform, according to one illustrated embodiment.

FIG. 23 is a flow diagram illustrating a process of operating a medical study data uploader (MSDU) system of a medical analytics platform, according to one illustrated embodiment.

FIG. 24 is a flow diagram illustrating a process of operating a medical analytics platform including a medical study data uploader (MSDU) system, an analytics service provider (ASP) system and a trusted broker service (TBS) system, according to one illustrated embodiment.

FIG. 25 is a block diagram showing high level components that implement a supplemental data retrieval process, according to one non-limiting illustrated implementation.

FIG. 26 is a flow diagram showing the processing of a supplemental data retrieval request, according to one non-limiting illustrated implementation.

FIG. 27 is a block diagram showing high level components that implement a worklist enrichment process, according to one non-limiting illustrated implementation.

FIG. 28 is a sequence diagram showing high level flow of data retrieval and updates for a worklist enrichment process, according to one non-limiting illustrated implementation.

DETAILED DESCRIPTION

In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed embodiments. However, one skilled in the relevant art will recognize that embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with MRI machines, computer systems, server computers, and/or communications networks have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the embodiments.

Unless the context requires otherwise, throughout the specification and claims which follow, the word “comprise” and variations thereof, such as, “comprises” and “comprising” are synonymous with “including,” and are inclusive or open-ended (i.e., does not exclude additional, unrecited elements or method acts).

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the content clearly dictates otherwise. It should also be noted that the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.

The headings and Abstract of the Disclosure provided herein are for convenience only and do not interpret the scope or meaning of the embodiments.

Many of the implementations described herein take advantage of a 4-D flow MRI data set, which essentially captures MRI magnitude and phase information for a three-dimensional (3-D) volume over a period of time. This approach may allow capture or acquisition of MRI data sets without requiring breath holding or synchronization or gating to a patient's cardiac or pulmonary cycles. Instead, MRI data sets are captured or acquired, and imaging processing and analysis employed to derive the desired information, for example by re-binning acquired information based on the cardiac and pulmonary cycles. This essentially pushes what is normally time-intensive acquisition operations to the imaging processing and analysis stage. As way of a simplified analogy, in some respects such may be thought of as capturing a movie of the anatomical structure (e.g., chest, heart) without concern over a patient's pulmonary or cardiac cycles, the processing the captured movie to account for relative movement introduced by the pulmonary and cardiac cycles. The captured information includes both magnitude information, which is indicative of anatomical structure, and phase information which is indicative of velocity. The phase information allows distinction between static and non-static tissue, for example allowing non-static tissue (e.g., blood, air) to be distinguished from static tissue (e.g., fat, bone). The phase information also allows certain non-static tissue (e.g., air) to be distinguished from other non-static tissue (e.g., blood). This may advantageously allow automated or even autonomous segmentation between tissues, and/or distinguishing atrial blood flow from venous blood flow. This may advantageously allow automated or even autonomous generation of flow visualization information, which may be superimposed on anatomical information. This may also advantageously allow automated or even autonomous flow quantification, identifying abnormalities and/or verifying results.

The workflow may generally be divided into three portions, sequentially: 1) image acquisition, 2) image reconstruction, and 3) image processing or post-processing and analysis. Alternatively, the workflow may be divided into 1) operational, 2) preprocessing, and 3) visualization and quantification.

Image acquisition may include determining, defining, generating or otherwise setting one or more pulse sequences, which are used to run the MRI machine (e.g., control magnets) and acquire raw MRI. Use of a 4-D flow pulse sequence allows capture of not only anatomical structure, which is represented by magnitude, but of velocity, which is represented by phase. At least one of the methods or techniques described herein, generation of patient specific 4-D pulse sequences, occurs during or as part of image acquisition portion. Image reconstruction may, for example, employ fast Fourier transformations, and result in MRI data sets, often in a form compatible with the DICOM standard. Image reconstruction has traditionally been computationally intensive often relying on supercomputers. The requirement for such is a significant burden to many clinical facilities. Many of the methods and techniques described herein occur during or as part of the imaging processor or post-processing and analysis. Such can include error detection and/or error correction, segmentation, visualization including fusion of flow related information and images of anatomical structures, quantification, identification of abnormalities including shunts, verification including identification of spurious data. Alternatively, error detection and/or error correction may occur during the preprocessing portion.

FIG. 1 shows a networked environment 100 according to one illustrated embodiment, in which one or more MRI acquisition systems (one shown) 102 are communicatively coupled to at least one image processing and analysis system 104 via one or more networks 106 a, 106 b (two shown, collectively 106).

The MRI acquisition system 102 is typically located at a clinical facility, for instance a hospital or dedicated medical imaging center. Various techniques and structures, as explained herein, may advantageously allow the image processing and analysis system 104 to be remotely located from the MRI acquisition system 102. The image processing and analysis system 104 may, for example, be located in another building, city, state, province or even country.

The MRI acquisition system 102 may, for example, include an MRI machine 108, a computer system 110 and an MRI operator's system 112. The MRI machine 108 may include a main magnet 114, which is typically an annular array of coils having a central or longitudinal bore 116. The main magnet 108 is capable of producing a strong stable magnetic field (e.g., 0.5 Tesla to 2.0 Tesla). The bore 116 is sized to receive at least a portion of an object to be imaged, for instance a human body 118. When used in medical imaging applications, the MRI machine 108 typically includes a patient table 120 which allows a prone patient 118 to be easily slid or rolled into and out of the bore 116.

The MRI machine also includes a set of gradient magnets 122 (only one called out). The gradient magnets 122 produce a variable magnetic field that is relatively smaller than that produced by the main magnet 114 (e.g., 180 Gauss to 270 Gauss), allowing selected portions of an object (e.g., patient) to be imaged.

MRI machine 108 also include radio frequency (RF) coils 124 (only one called out) which are operated to apply radiofrequency energy to selected portions of the object (e.g., patient 118) to be imaged. Different RF coils 124 may be used for imaging different structures (e.g., anatomic structures). For example, one set of RF coils 124 may be appropriate for imaging a neck of a patient, while another set of RF coils 124 may be appropriate for imaging a chest or heart of the patient. MRI machines 108 commonly include additional magnets, for example resistive magnets and/or permanent magnets.

The MRI machine 108 typically includes, or is communicatively coupled to, a processor-based MRI control system 126 used to control the magnets and/or coils 114, 122, 124. The processor-based control system 126 may include one or more processors, non-transitory computer- or processor-readable memory, drive circuitry and/or interface components to interface with the MRI machine 108. The processor-based control system 126 may, in some implementations, also perform some preprocessing on data resulting from the MRI operation.

An MRI operator's system 128 may include a computer system 130, monitor or display 132, keypad and/or keyboard 134, and/or a cursor control device such as a mouse 136, joystick, trackpad, trackball or the like. The MRI operator's system 128 may include or read computer- or processor executable instructions from one or more non-transitory computer- or processor-readable medium, for instance spinning media 138 such as a magnetic or optical disk. The operator's system 128 may allow a technician to operate the MRI machine 108 to capture MRI data from a patient 118. Various techniques, structures and features described herein may allow MRI machine 108 operation by a technician without requiring the presence of a clinician or physician. Such may advantageously significantly lower costs of MRI procedures. Also as described herein, various techniques, structures and features may allow MRI procedures to be performed much more quickly than using conventional techniques. Such may advantageously allow higher throughput for each MRI installation, amortizing cost of the capital intensive equipment over a much larger number of procedures. For example, high computational power computers may be located remotely from the clinical setting, and may be used to serve multiple clinical facilities. The various techniques, structures and features described herein may also additionally or alternatively advantageously reduce the time that each patient is exposed to the MRI procedure, reducing or alleviating the anxiety that often accompanies undergoing an MRI procedure. For instance, eliminating the need for breath holding and/or synchronizing with a patient's pulmonary and/or cardiac cycles via image processing and analysis techniques described herein may significantly reduce the time for acquisition, for example to eight to ten minutes.

The image processing and analysis system 104 may include one or more servers 139 to handle incoming requests and responses, and one or more rendering or image processing and analysis computers 140. The server(s) 139 may, for example take the form of one or more server computers, workstation computers, supercomputers, or personal computers, executing server software or instructions. The one or more rendering or image processing and analysis computers 140 may take the form of one or more computers, workstation computers, supercomputers, or personal computers, executing image processing and/or analysis software or instructions. The one or more rendering or image processing and analysis computers 140 will typically employ one, and preferably multiple, graphical processing units (GPUs) or GPU cores.

The image processing and analysis system 104 may include one or more non-transitory computer-readable medium 142 (e.g., magnetic or optical hard drives, RAID, RAM, Flash) that stores processor-executable instructions and/or data or other information. The image processing and analysis system 104 may include one or more image processing and analysis operator's systems 144. The image processing and analysis operator's system 144 may include a computer system 146, monitor or display 148, keypad and/or keyboard 150, and/or a cursor control device such as a mouse 152, joystick, trackpad, trackball or the like. The image processing and analysis operator's system 144 may be communicatively coupled to the rendering or image processing and analysis computer(s) 140 via one or more networks, for instance a LAN 154. While many image processing techniques and analysis may be fully automated, the image processing and analysis operator's system may allow a technician to perform certain image processing and/or analysis operations on MRI data captured from a patient.

While illustrated as a single nontransitory computer- or processor-readable storage medium 142, in many implementations the nontransitory computer- or processor-readable storage medium 142 may constitute a plurality of nontransitory storage media. The plurality of nontransitory storage media may be commonly located at a common location, or distributed at a variety of remote locations. Thus, a database of raw MRI data, preprocessed MRI data and/or processed MRI data may be implemented in one, or across more than one, nontransitory computer- or processor-readable storage media. Such database(s) may be stored separately from one another on separate computer- or processor-readable storage medium 142 or may be stored on the same computer- or processor-readable storage medium 142 as one another. The computer- or processor-readable storage medium 142 may be co-located with the image processing and analysis system 104, for example, in the same room, building or facility. Alternatively, the computer- or processor-readable storage medium 142 may be located remotely from the image processing and analysis system 104, for example, in a different facility, city, state or country. Electronic or digital information, files or records or other collections of information may be stored at specific locations in non-transitory computer- or processor-readable media 142, thus are logically addressable portions of such media, which may or may not be contiguous.

As noted above, the image processing and analysis system 104 may be remotely located from the MRI acquisition system 102. The MRI acquisition system 102 and the image processing and analysis system 104 are capable of communications, for example via one or more communications channels, for example local area networks (LANs) 106 a and Wide Area Networks (WANs) 106 b. The networks 106 may, for instance include packet switched communications networks, such as the Internet, Worldwide Web portion of the Internet, extranets, and/or intranets. The networks 106 may take the form of various other types of telecommunications networks, such as cellular phone and data networks, and plain old telephone system (POTS) networks. The type of communications infrastructure should not be considered limiting.

As illustrated in FIG. 1, the MRI acquisition system 102 is communicatively coupled to the first LAN 106 a. The first LAN 106 a may be a network operated by or for the clinical facility, providing local area communications for the clinical facility. The first LAN 106 a is communicatively coupled to the WAN (e.g., Internet) 106 b. A first firewall 156 a may provide security for the first LAN.

Also as illustrated in FIG. 1, the image processing and analysis system 104 is communicatively coupled to the second LAN 154. The second LAN 154 may be a network operated by or for an image processing facility or entity, providing local area communications for the image processing facility or entity. The second LAN 154 is communicatively coupled to the WAN 106 b (e.g., Internet). A second firewall 156 b may provide security for the second LAN 154.

The image processing facility or entity may be independent from the clinical facility, for example an independent business providing services to one, two or many clinical facilities.

While not illustrated, the communications network may include one or more additional networking devices. The networking devices may take any of a large variety of forms, including servers, routers, network switches, bridges, and/or modems (e.g., DSL modem, cable modem), etc.

While FIG. 1 illustrates a representative networked environment 100, typical networked environments may include many additional MRI acquisition systems, image processing and analysis system 104, computer systems, and/or entities. The concepts taught herein may be employed in a similar fashion with more populated networked environments than that illustrated. For example, a single entity may provide image processing and analysis services to multiple diagnostic entities. One or more of the diagnostic entities may operate two or more MRI acquisition systems 102. For example, a large hospital or dedicated medical imaging center may operate two, three or even more MRI acquisition systems at a single facility. Typically, the entity that provides the image processing and analysis services will operate multiple entity may provide image processing and analysis systems 104 which may include two, three or even hundreds of rendering or image processing and analysis computers 140.

FIG. 2 shows a networked environment 200 comprising one or more image processing and analysis systems 104 (only one illustrated) and one or more associated nontransitory computer- or processor-readable storage medium 204 (only one illustrated). The associated nontransitory computer- or processor-readable storage medium 204 is communicatively coupled to the image processing and analysis system(s) 104 via one or more communications channels, for example, one or more parallel cables, serial cables, or wireless channels capable of high speed communications, for instance, via FireWire®, Universal Serial Bus® (USB) 2 or 3, and/or Thunderbolt®, Gigabyte Ethernet®.

The networked environment 200 also comprises one or more end MRI acquisition systems 102 (only one illustrated). The MRI acquisition system(s) 102 are communicatively coupled to the image processing and analysis system(s) 104 by one or more communications channels, for example, one or more wide area networks (WANs) 210, for instance the Internet or Worldwide Web portion thereof.

In operation, the MRI acquisition systems 102 typically function as a client to the image processing and analysis system 104. In operation, the image processing and analysis systems 104 typically functions as a server to receive requests or information (e.g., MRI data sets) from the MRI acquisition systems 102. Described herein is an overall process which employs an asynchronous command and imaging pipeline that allows the image processing and analysis to be performed remotely (e.g., over a WAN) from the MRI acquisition system 102. This approach provides for a number of distinctive advantages, for instance allowing the MRI acquisition system(s) 102 to be operated by a technician without requiring the presence of a clinician (e.g., physician). Various techniques or approaches are also described to enhance security, while allowing access to medical imaging data as well as private patient specific health information.

While illustrated as located remotely from the MRI acquisition system(s) 102, in some implementations the image processing and analysis systems 104 may be co-located with the MRI acquisition system 102. In other implementations, one or more of the operations or functions described herein may be performed by the MRI acquisition system 102 or via a processor-based device co-located with the MRI acquisition system 102.

The image processing and analysis systems 104 receive MRI data sets, perform image processing on the MRI data sets, and provide the processed MRI data sets, for example to a clinician for review. The image processing and analysis systems 104 may, for example, perform error detection and/or correction on MRI data sets, for example phase error correction, phase aliasing detection, signal unwrapping, and/or detection and/or correction of various artifacts. Phase error is related to phase, as is phase aliasing. Signal unwrapping is related to magnitude. Various other artifacts may be related to phase and/or magnitude.

The image processing and analysis systems 104 may, for example, perform segmentation, distinguishing between various tissue type. The image processing and analysis systems 104 may, for example, perform quantification, for instance comparing blood flow into and out of a closed anatomical structure or through two or more anatomical structures. The image processing and analysis systems 104 may advantageously use quantification to verify results, for example confirming identification of a certain tissue and/or providing an indication of an amount of certainty in the results. Additionally, the image processing and analysis systems 104 may advantageously use quantification to identify the existence of a shunt.

In some implementations, the image processing and analysis systems 104 may generate images which reflect blood flow, for example including distinguishing between arterial and venous blood flow. For instance, the image processing and analysis systems 104 may employ a first color map (e.g., blue) to indicate arterial blood flow and a second color map (e.g., red) to indicate venous blood flow. The image processing and analysis systems 104 may indicate aberrations (e.g., shunt) using some other, distinctive color or visual emphasis. Numerous different techniques are described for distinguishing between different tissues as wells as between arterial and venous blood flow. Flow visualization may be superimposed, for instance as one or more layers, on or over visual representations of anatomical structure or magnitude data.

In some implementations, the image processing and analysis systems 104 may generate a patient specific 4-D flow protocol for use in operating an MRI acquisition system 102 with a specific patient. Such may include setting an appropriate velocity encoding (VENC) for operation of the MRI machine.

The image processing and analysis systems 104 may perform one or more of these operations or functions autonomously, without human input. Alternatively, the image processing and analysis systems 104 may perform one or more of these operations or functions based on human input, for example human input which identifies a point, location or plane, or which otherwise identifies a characteristic of anatomical tissue. Some planes and/or views may be predefined, allowing the operator, user or clinician to simply select a plane (e.g., a valve plane) or a denominated view (e.g., 2 chamber view, 3 chamber view, 4 chamber view) to quickly and easily obtain the desired view.

The networked environment 200 may employ other computer systems and network equipment, for example, additional servers, proxy servers, firewalls, routers and/or bridges. The image processing and analysis systems 104 will at times be referred to in the singular herein, but this is not intended to limit the embodiments to a single device since in typical embodiments there may be more than one image processing and analysis systems 104 involved. Unless described otherwise, the construction and operation of the various blocks shown in FIG. 2 are of conventional design. As a result, such blocks need not be described in further detail herein, as they will be understood by those skilled in the relevant art.

The image processing and analysis systems 104 may include one or more processing units 212 a, 212 b (collectively 212), a system memory 214 and a system bus 216 that couples various system components, including the system memory 214 to the processing units 212. The processing units 212 may be any logic processing unit, such as one or more central processing units (CPUs) 212 a, digital signal processors (DSPs) 212 b, application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc. The system bus 216 can employ any known bus structures or architectures, including a memory bus with memory controller, a peripheral bus, and/or a local bus. The system memory 214 includes read-only memory (“ROM”) 218 and random access memory (“RAM”) 220. A basic input/output system (“BIOS”) 222, which can form part of the ROM 218, contains basic routines that help transfer information between elements within the image processing and analysis system(s) 104, such as during start-up.

The image processing and analysis system(s) 104 may include a hard disk drive 224 for reading from and writing to a hard disk 226, an optical disk drive 228 for reading from and writing to removable optical disks 232, and/or a magnetic disk drive 230 for reading from and writing to magnetic disks 234. The optical disk 232 can be a CD-ROM, while the magnetic disk 234 can be a magnetic floppy disk or diskette. The hard disk drive 224, optical disk drive 228 and magnetic disk drive 230 may communicate with the processing unit 212 via the system bus 216. The hard disk drive 224, optical disk drive 228 and magnetic disk drive 230 may include interfaces or controllers (not shown) coupled between such drives and the system bus 216, as is known by those skilled in the relevant art. The drives 224, 228 and 230, and their associated computer-readable media 226, 232, 234, provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the image processing and analysis system(s) 104. Although the depicted image processing and analysis systems 104 is illustrated employing a hard disk 224, optical disk 228 and magnetic disk 230, those skilled in the relevant art will appreciate that other types of computer-readable media that can store data accessible by a computer may be employed, such as WORM drives, RAID drives, magnetic cassettes, flash memory cards, digital video disks (“DVD”), Bernoulli cartridges, RAMs, ROMs, smart cards, etc.

Program modules can be stored in the system memory 214, such as an operating system 236, one or more application programs 238, other programs or modules 240 and program data 242. Application programs 238 may include instructions that cause the processor(s) 212 to perform image processing and analysis on MRI image data sets. For example, the application programs 238 may include instructions that cause the processor(s) 212 to perform phase error correction on phase or velocity related data. For example, the application programs 238 may include instructions that cause the processor(s) 212 to correct for phase aliasing. Also for example, the application programs 238 may include instructions that cause the processor(s) 212 to perform signal unwrapping. Additionally or alternatively, the application programs 238 may include instructions that cause the processor(s) 212 to identify and/or correct for artifacts.

The application programs 238 may include instructions that cause the processor(s) 212 to, for example, perform segmentation, distinguishing between various tissue type. The application programs 238 may include instructions that cause the processor(s) 212 to perform quantification, for instance comparing blood flow into and out of a closed anatomical structure or through two or more anatomical structures. The application programs 238 may include instructions that cause the processor(s) 212 to use quantification to verify results, for example confirming identification of a certain tissue and/or providing an indication of an amount of certainty in the results. The application programs 238 may include instructions that cause the processor(s) 212 to use quantification to identify the existence of a shunt.

The application programs 238 may include instructions that cause the processor(s) 212 to generate images which reflect blood flow, for example distinguishing between arterial and venous blood flow. For instance, a first color map (e.g., blue) may be used to indicate arterial blood flow and a second color map (e.g., red) to indicate venous blood flow. Aberrations (e.g., shunt) may be indicated using some other, distinctive color or visual emphasis. Color transfer functions may be applied to generate the color maps. The application programs 238 may include instructions that cause the processor(s) 212 to superimpose visualization of flow (e.g., MRI phase data indicative of blood flow velocity and/or volume) on visualization or rendered images of anatomy (e.g., MRI magnitude data). The instructions may cause the flow visualization to be rendered as one or more layers on the images of the anatomy to provide a fusion of anatomy (i.e., magnitude) and flow (i.e., phase) information, for example as a color heat map and/or as vectors (e.g., arrow icons) with direction and magnitude (e.g., represented by length, line weight). The instructions may additionally or alternatively cause the generation of spatial mappings or visualization of signal dispersion, turbulence and/or pressure, which may be overlaid or superimposed on a spatial mapping or visualization of anatomical structure. Fusing visualization of phase or velocity related information with visualization of anatomical information or visual representations of anatomical structures may facilitate the identification of anatomical landmarks. The instructions may make use of sets or arrays of graphics processing units or GPUs to quickly render the visualizations.

Transfer functions may also be applied to determine which visual effects (e.g., color) to apply to which tissue. For example, arterial blood flow may be colored in shades of blue and venous blood flow in shades of red, while fat tissue colored as yellow. Anatomical structure, represented as magnitude in the MRI image data set, may, for example, be visualized using grey scale. Depth of view may be operator or user adjustable, for example via a slider control on a graphical user interface. Thus, visualization may be in the form a fusion view that advantageously fuses a visual representation of velocity information with a visual representation of anatomical information or representation.

The application programs 238 may include instructions that cause the processor(s) 212 to generate a patient specific 4-D flow protocol for use in operating an MRI acquisition system 102 with a specific patient. Such may be based on patient specific input, for example provided by a technician, and may be based on the particular MRI machine being used to capture the MRI data set.

The application programs 238 may include instructions that cause the processor(s) 212 to receive image data sets from the MRI acquisition system, process and/or analyze the image data sets, and provide processed and/or analyzed images and other information to users remotely located from the image processing, in a time sensitive and secure manner. Such is described in detail herein with reference to the various Figures.

The system memory 214 may also include communications programs, for example, a server 244 that causes the image processing and analysis system(s) 104 to serve electronic information or files via the Internet, intranets, extranets, telecommunications networks, or other networks as described below. The server 244 in the depicted embodiment is markup language based, such as Hypertext Markup Language (HTML), Extensible Markup Language (XML) or Wireless Markup Language (WML), and operates with markup languages that use syntactically delimited characters added to the data of a document to represent the structure of the document. A number of suitable servers may be commercially available such as those from Mozilla, Google, Microsoft and Apple Computer.

While shown in FIG. 2 as being stored in the system memory 214, the operating system 236, application programs 238, other programs/modules 240, program data 242 and server 244 can be stored on the hard disk 226 of the hard disk drive 224, the optical disk 232 of the optical disk drive 228 and/or the magnetic disk 234 of the magnetic disk drive 230.

An operator can enter commands and information into the image processing and analysis system(s) 104 through input devices such as a touch screen or keyboard 246 and/or a pointing device such as a mouse 248, and/or via a graphical user interface. Other input devices can include a microphone, joystick, game pad, tablet, scanner, etc. These and other input devices are connected to one or more of the processing units 212 through an interface 250 such as a serial port interface that couples to the system bus 216, although other interfaces such as a parallel port, a game port or a wireless interface or a universal serial bus (“USB”) can be used. A monitor 252 or other display device is coupled to the system bus 216 via a video interface 254, such as a video adapter. The image processing and analysis system(s) 104 can include other output devices, such as speakers, printers, etc.

The image processing and analysis systems 104 can operate in a networked environment 200 using logical connections to one or more remote computers and/or devices. For example, the image processing and analysis 104 can operate in a networked environment 200 using logical connections to one or more MRI acquisition systems 102. Communications may be via a wired and/or wireless network architecture, for instance, wired and wireless enterprise-wide computer networks, intranets, extranets, and/or the Internet. Other embodiments may include other types of communications networks including telecommunications networks, cellular networks, paging networks, and other mobile networks. There may be any variety of computers, switching devices, routers, bridges, firewalls and other devices in the communications paths between the image processing and analysis systems 104, the MRI acquisition systems 102.

The MRI acquisition systems 102 will typically take the form of an MRI machine 108 and one or more associated processor-based devices, for instance an MRI control system 126 and/or MRI operator's system 128. The MRI acquisition systems 102 capture MRI information or data sets from patients. Thus, in some instances the MRI acquisition systems 102 may be denominated as front end MRI acquisition systems or MRI capture systems, to distinguish such from the MRI image processing and analysis system(s) 104, which in some instances may be denominated as MRI backend systems. The MRI acquisition systems 102 will at times each be referred to in the singular herein, but this is not intended to limit the embodiments to a single MRI acquisition system 102. In typical embodiments, there may be more than one MRI acquisition system 102 and there will likely be a large number of MRI acquisition systems 102 in the networked environment 200.

The MRI acquisition systems 102 may be communicatively coupled to one or more server computers (not shown). For instance, MRI acquisition systems 102 may be communicatively coupled via one or more diagnostic facility server computers (not shown), routers (not shown), bridges (not shown), LANs 106 a (FIG. 1), etc., which may include or implement a firewall 156 a (FIG. 1). The server computers (not shown) may execute a set of server instructions to function as a server for a number of MRI acquisition systems 102 (i.e., clients) communicatively coupled via a LAN 106 a at a clinical facility or site, and thus act as intermediaries between the MRI acquisition systems 102 and the MRI image processing and analysis system(s) 104. The MRI acquisition systems 102 may execute a set of client instructions to function as a client of the server computer(s), which are communicatively coupled via a WAN.

The MRI control system 126 typically includes one or more processor (e.g., microprocessors, central processing units, digital signal processors, graphical processing units) and non-transitory processor-readable memory (e.g., ROM, RAM, Flash, magnetic and/or optical disks). The MRI operator's system 128 may take the form of a computer, for instance personal computers (e.g., desktop or laptop computers), net book computers, tablet computers, smart phones, personal digital assistants, workstation computers and/or mainframe computers, and the like, executing appropriate instructions.

The MRI operator's system 128 may include one or more processing units 268, system memories 269 and a system bus (not shown) that couples various system components including the system memory 269 to the processing unit 268.

The processing unit 268 may be any logic processing unit, such as one or more central processing units (CPUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), graphical processing units (GPUs), etc. Non-limiting examples of commercially available computer systems include, but are not limited to, an 80x86 or Pentium series microprocessor from Intel Corporation, U.S.A., a PowerPC microprocessor from IBM, a Sparc microprocessor from Sun Microsystems, Inc., a PA-RISC series microprocessor from Hewlett-Packard Company, a 68xxx series microprocessor from Motorola Corporation, an ATOM processor, or an A4 or A5 processor. Unless described otherwise, the construction and operation of the various blocks of the MRI acquisition systems 102 shown in FIG. 2 are of conventional design. As a result, such blocks need not be described in further detail herein, as they will be understood by those skilled in the relevant art.

The system bus can employ any known bus structures or architectures, including a memory bus with memory controller, a peripheral bus, and a local bus. The system memory 269 includes read-only memory (“ROM”) 270 and random access memory (“RAM”) 272. A basic input/output system (“BIOS”) 271, which can form part of the ROM 270, contains basic routines that help transfer information between elements within the MRI acquisition systems 102, such as during start-up.

The MRI operator's system 128 may also include one or more media drives 273, e.g., a hard disk drive, magnetic disk drive, WORM drive, and/or optical disk drive, for reading from and writing to computer-readable storage media 274, e.g., hard disk, optical disks, and/or magnetic disks. The nontransitory computer-readable storage media 274 may, for example, take the form of removable media. For example, hard disks may take the form of a Winchester drive, and optical disks can take the form of CD-ROMs, while magnetic disks can take the form of magnetic floppy disks or diskettes. The media drive(s) 273 communicate with the processing unit 268 via one or more system buses. The media drives 273 may include interfaces or controllers (not shown) coupled between such drives and the system bus, as is known by those skilled in the relevant art. The media drives 273, and their associated nontransitory computer-readable storage media 274, provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for MRI acquisition system(s) 102. Although described as employing computer-readable storage media 274 such as hard disks, optical disks and magnetic disks, those skilled in the relevant art will appreciate that MRI operator's system(s) 128 may employ other types of nontransitory computer-readable storage media that can store data accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks (“DVD”), Bernoulli cartridges, RAMs, ROMs, smart cards, etc. Data or information, for example, electronic or digital files or data or metadata related to such can be stored in the nontransitory computer-readable storage media 274.

Program modules, such as an operating system, one or more application programs, other programs or modules and program data, can be stored in the system memory 269. Program modules may include instructions for accessing a Website, extranet site or other site or services (e.g., Web services) and associated Webpages, other pages, screens or services hosted or provided by the MRI processing and analysis system(s) 104.

In particular, the system memory 269 may include communications programs that permit the MRI acquisition system(s) 102 to exchange electronic or digital information or files or data or metadata with the MRI image processing and/or analysis services provided by the MRI processing and analysis system(s) 104. The communications programs may, for example, be a Web client or browser that permits the MRI acquisition system(s) 102 to access and exchange information, files, data and/or metadata with sources such as Web sites of the Internet, corporate intranets, extranets, or other networks. Such may require that an end user client have sufficient right, permission, privilege or authority for accessing a given Website, for example, one hosted by the MRI processing and analysis system(s) 104. As discussed herein, patient identifying data may reside on systems operated by or for the clinical facility, and may not be accessible by or through the systems operated by or for the image processing facility or the image processing facility personnel. The browser may, for example, be markup language based, such as Hypertext Markup Language (HTML), Extensible Markup Language (XML) or Wireless Markup Language (WML), and may operate with markup languages that use syntactically delimited characters added to the data of a document to represent the structure of the document.

While described as being stored in the system memory 269, the operating system, application programs, other programs/modules, program data and/or browser can be stored on the computer-readable storage media 274 of the media drive(s) 273. An operator can enter commands and information into the MRI operator's system(s) 128 via a user interface 275 through input devices such as a touch screen or keyboard 276 and/or a pointing device 277 such as a mouse. Other input devices can include a microphone, joystick, game pad, tablet, scanner, etc. These and other input devices are connected to the processing unit 269 through an interface such as a serial port interface that couples to the system bus, although other interfaces such as a parallel port, a game port or a wireless interface or a universal serial bus (“USB”) can be used. A display or monitor 278 may be coupled to the system bus via a video interface, such as a video adapter. The MRI operator system(s) 128 can include other output devices, such as speakers, printers, etc.

The MRI image processing and analysis system may build a static interface, which allows various tissue types to be subtracted or added to an MRI 4-D flow data set. For example, static tissues such as fat or bone may be distinguished from non-static tissues such as air or flowing blood. The MRI image processing and analysis system may further autonomously distinguish between various non-static tissues, for instance distinguishing between air (e.g., lungs) and flowing blood. Further, the MRI image processing and analysis system may distinguish between arterial and venous blood flows.

For instance, the MRI image processing and analysis system may employ fast Fourier transformation to identify blood tissue, which is expected to have a pulsatile pattern or waveform. Air or lung will tend to have a random appear pattern over a defined volume, as velocity of neighboring voxels are compared. For instance, voxels with strong or fast velocities are typically indicative or air. The MRI data sets may be rather large, for example 256×256×256×20 time points. The MRI image processing and analysis system may rely on gradients (e.g., gradient descent method) to detect different tissue types, and may advantageously employ a numerical approach rather than an analytic solution approach to quickly handle the relatively large MRI data sets. By controlling the number of significant digits (e.g., 2) of the numerical approach, the MRI image processing and analysis system may achieve very fast (e.g., 1 second as opposed to 30 minutes) results, while still obtaining results that are sufficiently accurate for the particular application.

In some implementations, different tissue types may be subtracted from the patient MRI data set, one at a time. For example, subtracting air or lung, subtracting blood, separating atrial from venous flow, subtracting bone, leaving fat. Notably, fat is static, so each voxel representing fat should have zero velocity associated therewith. The MRI image processing and analysis system may advantageously employ such a ground truth to correct MRI data set for all tissue types.

If a non-zero velocity is found for fat type tissue, this can be used to adjust the entire set of data (e.g., for all tissue). For example, the MRI image processing and analysis system may generate or create a polynomial model based on an identified area or volume (e.g., fat or soft tissue). Such may be a simple polynomial (e.g., ax²+bx+c) or a much more complex polynomial (e.g., non-rational uniform b-spline). The MRI image processing and analysis system may find the coefficients to the polynomial fits the image, for example using linear regression techniques or linear algebra techniques. This results in a model which the MRI image processing and analysis system may apply to (e.g., subtract from) the whole field, not just the fat or soft tissue.

In one implementations, a replica body is imaged to create a reference set of data or “phantom” model which can be subtracted from actually patient data. The replica body may be formed of materials that mimic the MRI response of an actually body, although will not have blood flow. A phase gradient in reference set of data or “phantom” model may represent noise (e.g., random noise), and can be used to correct a phase shift. This approach advantageously avoids the need to generate a polynomial fit to the 3-D data. The generated reference set or phantom model may be valid over a number of months of MRI machine operation, although a new set of reference data or phantom model should be generated if the MRI machine is serviced or moved.

The MRI image processing and analysis system may define various filters or mask for removing different tissue types or for removing either venous or atrial blood flow. Filters or masks may remove anomalous blood flow, such as blood flow outside some reasonable range (e.g., too high or fast, too slow or low) or where blood appears to be flowing in an anatomical structure (e.g., bone) where there should be no blood flow. A filter or mask may also be defined to display only voxels having magnitudes with an absolute value greater than some threshold value. A filter or mask may also be defined to display only voxels with an absolute value of the cross product of magnitude and a velocity vector which absolute value is greater than some defined threshold. Further a filter or mask may be defined that shows only voxels having vectors in a same direction as the vectors of neighboring voxels, to for instance identify or view high velocity jets. Notably, velocity vectors of neighboring voxels are in different directions may be an indication of noise.

Pre-Processing Mass Conservation Correction Error Reduction

The goal of this pre-processing algorithm is to correct the flow data (segmentation, flow quantification, and background phase error correction). There are 3 flow datasets that need to be corrected: i) x velocity, ii) y velocity, and iii) z velocity. Due to imaging artifacts (e.g., turbulence) and noise, the flow data will be biased. To correct for this, mass conservation (i.e., physical principles) is used to correct the flow data. Mass conservation tells us that the mass of a closed system must remain constant over time, as system mass cannot change quantity if it is not added or removed. Therefore, if a boundary is defined within the heart (i.e., luminal border of the heart chambers and vessels), the flow entering a stationary volume must match the flow exiting the volume if the fluid is incompressible. This theory can be applied to any volume. In the case of blood flow, we make assumptions that the blood density is constant, and therefore the continuity equation simplifies to mean that the divergence of velocity field is zero everywhere. Physically, this is equivalent to saying that the local volume dilation rate is zero (i.e., du/dx+dv/dy+dw/dz=0). It is impossible to force this condition everywhere, but the local volume dilation can be minimized over all time points. There are several different types of algorithms that will minimize du/dx+dv/dy+dw/dz, but the most common is an algorithm that will generate a least squares divergence free approximation of the flow field. There are several ways to construct a least squares approximation to the flow field with the constraint of minimizing the divergence, and several different algorithms to achieve this.

Typically there is an iterative approach involved that tries to minimize the residual divergence with every pass. In addition, knowing the exact boundary of the vessel/chamber is important to ensure zero flux through the boundary. Without said boundary, flow could be allowed to escape into the heart muscle and fat. In addition, there could be artifact in the image (i.e., caused by turbulence). If a user identifies a region where there is artifact (“bad data”), this region is not used to influence the velocity value correction in the “good data” region.

Another approach to solve this is using optimization: attempting to minimize divergence while ensuring the original vector field is changed as little as possible (to still capture local effects and prevent smoothing).

Conservation of momentum can be applied in a later act to estimate pressure gradients across a vessel in addition to wall shear stress. This mass conservation step is critical to ensure accurate pressure estimations.

Automatic Phase Aliasing Correction Using Time Domain

Phase aliasing occurs when the VENC that was set for the 4-D flow scan was too low causing the velocity values to “wrap”; from large positive values to large negative values or vice versa. In principle, this wrapping can happen more than once.

By analyzing the overall time variation of velocity data it is possible to determine the main points of the cardiac cycle (described elsewhere). Under the assumption that there is no velocity aliasing in the image at peak diastole and also under the assumption that velocity at a single point in space does not, in reality, vary by more than +/−VENC from one time point to the next, one is able to correct for phase aliasing by examining the time variation of each point in space as follows:

i) Identify the peak diastole time point and assume that there is no phase aliasing at that point.

ii) Examine the time behavior of each acquired velocity component individually.

iii) For each point in space (voxel) in each velocity image track the change in velocity from one time point to the next. If the velocity is observed to vary by more than +/−VENC assume that aliasing has occurred.

iv) When aliasing is detected the wrap count for that point is either incremented if observed velocity reduced by more than VENC or decremented if the observed velocity increased by more than VENC.

v) At each point in time the velocity is altered according to the current accumulated wrap count for that point by adding the product of wrap count with two times VENC.

vi) Check that wrap count has returned to a value of zero once the current time point has return to the initial peak diastole starting point. If wrap count has not returned to zero, then the processing of that point in space (voxel) should be considered to be an error.

The method can be improved and made more performant by using other methods to determine the pixels of interest. For example, one may use other methods to determine the pixels that are most likely to represent blood flow and only process these pixels.

This method also has the characteristic and advantage of being self-diagnosing. The wrap count for all valid blood voxels (as opposed to air, for example) should return to zero when the processing for that voxel over time has finished. Errors can be kept track of on a voxel by voxel basis though this has the weakness that this method of error detection is not guaranteed to catch every error voxel. However, in addition, by looking for a low overall error rate as a fraction of the number of pixels where corrections were applied, one can ascertain whether or not the necessary initial assumptions, required by the method, are largely correct.

Automatic Phase Aliasing Correction

Phase aliasing occurs when the VENC that was set for the 4-D flow scan was too low. It is very easy to find voxels that have been aliased because of the following:

i) The VENC of each scan is known since this information is in the header file of all the DICOM images.

ii) Identify sharp changes in flow velocity around the +/−VENC velocity (i.e., if VENC is set at 100 cm/s, look for sharp changes in velocity around +/−99 cm/s.) Sharp changes in velocity means a voxel may have a velocity value of 100 cm/s, and the adjacent voxel has a value of −99 cm/s.

iii) Then find the border of the aliased region by connecting all the voxels that have a sharp gradient around +/−VENC.

iv) This results in an enclosed boundary. Determine if all the voxels in the region of the enclosed boundary are aliased. By starting at the boundary and moving toward the centroid of the 3-D region, the system can interrogate every voxel to ensure that there is no significant jump (across a VENC).

v) If no steep jump is encountered then the VENC velocity can be added to all voxels within the aliased region.

vi) If a steep jump is encountered, then the problem becomes a little more challenging (but still solvable). In this case, a voxel could be wrapped several times (i.e., if the VENC is set at 100 cm/s but the velocity at the voxel actually is 499 cm/s, this will be wrapped 2 times and the velocity will be shown as 99 cm/s). The way to correct the data is to look at the velocity of neighboring voxels. If there is a jump of more than 1.5 times the VENC, then 2*VENC needs to be added or subtracted in that enclosed region. The selection of adding or subtracting is chosen to minimize the discontinuity across the neighboring voxels.

vii) To improve the algorithm further, information about where static tissue is can be critical in defining where absolute zero must be. Since static tissue has 0 velocity, those voxels that are identified as being static tissue must not be wrapped. There then must be a continuous increase in speed away from the wall due to physical properties (i.e., fluid boundary layer). The only assumption in all of this is that neighboring voxels do not have more than a 1.5*VENC jump across one another.

Spline Real-Time Eddy Current Correction

When an MRI acquisition is performed the data can contain artifacts due to eddy currents in the magnetic field. In a 4-D flow acquisition in which particle velocity is acquired the artifacts will cause the velocity values to be incorrect. It is critical with 4-D flow to have accurate velocity data in order to quantify blood flow through vessels.

At least one technique for correcting the eddy current artifacts involves:

-   -   volumetric segmentation of static (zero velocity) tissues; and     -   using the velocity data at these static locations to fit a curve         to the volume that can be subtracted from the raw data.

Given a volume mask that represents the static tissue, 3-D blocks of arbitrary size are evaluated.

If a block within the volume contains enough masked voxels it is considered static tissue. The average velocity for each of the static tissue blocks is then used as control values for a collection of spline functions in each of the three primary axis directions. After evaluating all the spline functions in all three directions, the result is a regular grid of values that can be up-sampled to the original resolution and then subtracted from the original data. After subtraction, the static tissues should have an effective velocity of zero, and the non-static tissues will have eddy current artifacts removed. This will allow for accurate flow quantification.

Given a segmented volume, a new volume of significantly lower resolution was generated. The values in this new volume are the result of averaging values from the larger volume, however since some of the elements would be masked away by the segmentation, an element in the low-resolution volume might have significantly less high-resolution data and potentially no high-resolution data. Elements with no data or insufficient data are thrown out. The result at this point is a regular grid with holes in it. In order to evaluate the tensor product for the spline volume the initial pass evaluates spline basis functions for each row of elements wherein the order of the spline may vary due to the number of available control values. After the first pass, there will be no holes so the remainder of the tensor product can be evaluated. Based on the analysis of our test data, results from this new and innovative approach is a smooth 3-D time-varying function representing the error in the volume and is very fast to calculate.

For the third step, our approach to apply the correction algorithm was to use tri-linear sampling from the correction volume, which proved successful. For each element in the source volume we perform a tri-linear blend of eight elements in the correction volume and subtract that value from the source data. After applying our new correction function flow measurements were found to be within 3% error. In addition, as part of the process requires user interaction, the requirement for real-time performance was also met as evaluating and applying our new correction takes on the order of milliseconds instead of hours.

Solids for Background Phase Error Correction

The blood velocity information in the 4-D flow MRI scan has an error which needs to be corrected for in order to get accurate blood flow calculations. The error signal in the static tissue can be used to provide a correction function for the non-static tissue (described elsewhere). A three-dimensional volume of tissue called a solid can be created to identify a section of either static or non-static tissue. A solid can be created using two methods:

Orthogonal contours: The user can manually draw three intersecting closed contours. The intersection of these contours represents a solid, three-dimensional volume of either static or non-static tissue. The contours do not need to be perfectly orthogonal and the user can create the contours at any location.

3-D floods: The user can alternatively choose to automatically create a solid by specifying the starting point of a three-dimensional flood. The flood can be used on any image including phase images. The image is flooded based on a threshold below and above the value at the point where the user clicked. The user can control both the threshold and the radius of the flood that is generated.

Multiple solids can be created using either method to mask out areas of both static and non-static tissue and can be used overlapping each other to unmask areas within an existing solid.

In some situations there will be artifact in the images. Artifact needs to be removed or highlighted in order to prevent a user from giving an incorrect diagnosis. Our software has pre-processing steps (i.e., eddy current correction) that compute a metric based on all of the voxels in the dataset. To avoid these pre-processing steps a tool is used to identify voxels that have artifact, and these voxels are removed from any pre-processing step (but not removed for visualization purposes). The tool can be a manual segmentation tool (i.e., user circles areas that have artifact), or a semi-automatic/automatic segmentation tool that identifies artifact. Regardless of the tool specifics our software needs a feature to remove “bad voxels” from being quantified.

Automatic Background Phase Error Correction

Accurate measurement of velocity in 4-D flow MRI scans requires the application of corrections for the false signal introduced by eddy currents. Determining eddy current correction (ECC) is done by examining the velocity signal in static (non-moving) tissue. This requires the masking of all moving tissue, blood and air. This claim describes a method for doing this automatically, without user intervention. Automatic correction is useful as it not only makes the software simpler and quicker to use, it allows the correction to be precomputed and applied when the user first opens the study. It is also very important as it allows other preprocessing algorithms, doing things like automatic segmentation and measurement, to benefit from ECC.

Automatic ECC is done by computing initial starting values for three filters that the user is then free to adjust after the study is open. Air is masked by masking out regions with anatomy image values below a set threshold. This threshold is determined automatically by an analysis of the histogram for anatomy image values over the entire scanned volume. The histogram for these values over the chest cavity displays a pattern that allows for the automatic detection of the image values corresponding to air.

In addition, two filters have been developed that reliably detect regions of blood flow and regions of heart wall movement. The region of the heart can be satisfactorily masked out by appropriately setting these two filters. Due to the normalization used in the production of these filters along with their naturally consistent nature, satisfactory results can be obtained simply by setting these filters to predetermined values (for example, 50%). The automatic setting of these filters could be further improved (or tweaked) by analysis of the values produced by these filters, similar to what was described in the previous paragraph for the detection of regions of air. The settings could also be tweaked by examining the resulting ECC and looking for regions that show large variation over the cardiac cycle.

The correct values for these filters, determined when the study is preprocessed, are then simply stored in the database along with the other study information, allowing the client software to set these as the default values when the study is first opened.

Visualization Temporal Landmark Quantification and Visualization

It useful to be able to identify landmarks (i.e., points, lines, planes, areas, volumes) in the body and specifically in the heart. Several landmarks are dynamic in nature (e.g., mitral valve plane), and thus it is important to track their movement in time:

Points: Track 3-D path (which is a line) over time.

Lines: Track 3-D path of 2 endpoints over time.

Planes: Track a point on a plane and the plane's normal vector over time.

Areas: Track dilating contour, contour centroid, and contour normal vector over time.

Volumes: Discretize surface of volume and track each discretized point over time.

There are two acts to temporal landmark quantification and visualization:

1) Detection: The first step is to identify the landmarks over time. This can be done manually or automatically.

Manual detection: The user can indicate the position and orientation of each landmark. One method of doing this could be to navigate the image using pan and rotate so that the center of the image is at the desired location of the landmark. The location of the landmark can be different at different points in time and it will be interpolated for timepoints where the user has not explicitly set it. It is indicated to the user if a landmark is interpolated.

2) Display: Depending on the type of landmark a different type of method to display the data is used. For instance if a contour does not move or change its normal vector over time (i.e., just dilate), it makes sense for the user's view plane to not change and always be aligned with the contour. If this contour does move, we can imagine following the plane such that the view is always aligned with the plane for each time point. The view plane can be either from a Lagrangian perspective or from an Eulerian perspective. For volumes, an Eulerian perspective is more appropriate where the surface of a volume dilates and this can be visualized with a camera that is fixed in space (the user can change the camera location as needed).

Cardiac views: The left ventricle apex, right ventricle apex, mitral valve, tricuspid valve, aortic valve, and pulmonic valve can be used to create two-chamber, three-chamber, four-chamber, and short-axis views of both the right and left ventricles once the landmarks have been detected. The orientations of these views are specified in the Mayo Clinic Guide to Cardiac MR. An orientation and zoom level for each view can be calculated from the positions of the landmarks. If the landmark's position changes in time the view will change in time accordingly.

Example landmarks for each view:

Left two chamber: aortic valve, mitral valve, tricuspid valve, left ventricle apex

Left three chamber: aortic valve, mitral valve, left ventricle apex

Left four chamber: tricuspid valve, mitral valve, left ventricle apex

Left short axis: mitral valve, left ventricle apex

Right two chamber: pulmonic valve, tricuspid valve, mitral valve, right ventricle apex

Right three chamber: pulmonic valve, tricuspid valve, right ventricle apex

Right four chamber: tricuspid valve, mitral valve, right ventricle apex

Right short axis: tricuspid valve, right ventricle apex

Interactive Landmark Based Views

Once certain landmarks have been placed (e.g., aortic valve, mitral valve, left ventricle apex, anterior papillary muscle, posterior papillary muscle, pulmonary valve, tricuspid valve, right ventricle apex, LPA, RPA, SVC, IVC, descending aorta), automatic views can be created to display the anatomy of interest. Clinicians are used to viewing a certain landmark with 3 perpendicular views or in the case of the heart using a 4 chamber view or a left or right ventricle 2 or 3 chamber view. By updating the location of just 1 landmark for one of the time points, all views update accordingly such that either the views are always perpendicular or the 2, 3, and 4 chamber views remain intact. Once the landmarks have been placed, and the views generated automatically, these views can be saved in the report section of the software and exported in any format (i.e., an image) include a cine movie (i.e., multiple images over time).

4-D Mesh Creation from Closed Contours

Once contours have been placed along the short axis (possibly curved) for each time point, the mesh is then generated independently for each time point. This is done by rotating each contour in the short axis stack so as to minimize twisting, and then generating open cubic spline which connects the first point in each contour, a second spline that connects the second point, so on for each point in the contour (each slice's contour has the same number of points. The result of this process is a cylindrical grid of points which we use as the vertices of the mesh.

The process of minimizing twisting is done by computing an open cubic Hermite spline from the centroid of one contour to the centroid of the contour above, and then running this spline from each point on the lower contour until it intersects the plane the contour above it lies in. The system computes this intersection point and then determines which of these intersection points lies closest to an actual contour point in the upper contour. The contour is then rotated such that these two points will lie on the same long axis spline.

The current implementation works reasonably well with both curved and straight axes when the contours are reasonably circular and the difference between neighboring contours spatially is minimal. However, in the case of the right ventricle where the contours are not circular, excessive twisting is sometimes introduced by the current implementation. To minimize this, we should get rid of the long axis spline approach and switch to one where the number of triangles between any two slices may differ. Doing this minimizes twisting more locally which will result in an overall smoother mesh.

Snap to Flow Tool

Accurately observing or measuring the blood flow in a 4-D flow scan requires the user to align an MPR so that it is perpendicular to the direction of flow. This describes a method for creating a tool allowing the user to set the correct orientation of the MPR automatically.

In order to align an MPR the user first activates the tool and then clicks on a central region of the blood flow in question. The click points then serves as the center of rotation when the MPR is aligned, moving the click point to the center of the resulting MPR. Alignment is done by averaging the blood flow in a small region around the click point. To do this accurately, the measurement is done using the timepoint corresponding to peak blood flow, regardless of the timepoint that the user is currently viewing while using the tool. This generally implies doing the measurement at peak systole.

While the user is allowed to adjust the timepoint for peak systole, this point is first determined automatically by the executing software during preprocessing of the data set, and this automatic value is used as the default when the study is first opened by the user. A filter has been developed (described elsewhere) for automatically determining regions of blood flow within the scanned volume. Peak systole is then determined by examining the time dependence of the overall flow within the filtered or mask region determined to correspond to blood.

Once the direction of flow has been accurately determined it is straightforward to adjust the orientation of the MPR so that it is on a plane perpendicular to the flow.

Quantification Automatic Blood Flow Quantification

The blood flow in a chamber and/or vessel can be automatically quantified by first isolating the blood pool (see segmentation methods described in this document) and placing a plane on a landmark (that can be defined using the methods above) that is roughly perpendicular to the flow in the chamber/vessel (i.e., normal of plane is aligned with the flow). Once these 2 acts have been achieved, the intersection between the plane and blood pool creates a contour. All the voxels within the contour are flagged. Next is to sum the dot product of the plane's normal vector with the velocity vector of that voxel (in addition to normalizing by the area of the voxel) for every voxel to give the total flow. The flow at that contour can be automatically displayed on screen or in report that could be eventually exported.

Allowing a user to select a position on an image has many important applications. In performing measurements a user might want to measure the distance from one point to another. In an application that uses MPRs from a volume of data, the points on an image represent locations in 3-D space. These 3-D points are easy to compute from the metadata associated with the image. In an application that uses volume rendering, allowing a user to select a point in 3-D space is more difficult since each pixel could be at a different depth.

In typical front to back volume raycasting with an increasing alpha compositing function that terminates once alpha reaches 1.0, determining the depth of the pixel can be done by keeping track of where the ray terminates. When raycasting back to front, there is no early ray termination. The result color is simply updated based on the compositing function. Typically the compositing function will make air transparent and as such the color will stop changing as the ray exits the material closest to the eye. By keeping track of when the color stopped changing, this depth for each pixel can be used to transform the 2-D user selected coordinate back into a 3-D location in space. This 3-D location selection can be used to select a blood vessel and then automatically quantify flow.

Automatic Shunt Detection

Instead of trying to find an exact location for a shunt, the first operation would be to identify if a shunt exists. One simple method of identifying if a shunt is present is to measure the left heart flow (Qs) and the right heart flow (Qp). Qp and Qs can be measured either manually (e.g., by placing a contour) or automatically if landmarks and blood pool segmentation have been completed. If these numbers do not match within a certain threshold, the scan can be flagged as potentially having a shunt.

These measurements could be done automatically using the following technique:

i) Automatic measurement of cardiac output (Qs) is described elsewhere as is the production of masks for both aortic and pulmonic flow along with automatic estimates of the location of the aortic and pulmonic valves.

ii) Once the valve regions have been identified, it is a straightforward task to take them and the already determined pulmonic flow regions, move slightly downstream from the valve and produce flow measurement contours in a similar way to what has been described for cardiac output. Once suitable contours have been identified for measuring pulmonic flow the existing flow measurement algorithms can be used to determine the output from the right ventricle.

iii) Use the automatic flow measurement to indicate the likelihood that a shunt exists.

Automatic Detection of Peak and End Systole and Diastole

Much automatic processing depends on the ability to first identify the timepoints corresponding to the main temporal landmarks in the cardiac cycle: peak and end systole and diastole.

As described elsewhere, we are able to use a Fourier analysis technique on the velocity images in order to identify regions of blood flow within the heart along with the main arteries and veins around the heart. Once these main regions of blood flow have been identified, we find the total blood flow over the identified voxels at each point in time (typically 20 timepoints). The system is then able to analyze the resulting function of time to determine the landmarks in the cardiac cycle. The timepoint with the most flow is first assigned the peak systole landmark. From there the function is analyzed in both directions in time to determine the points where the flow tends to level off. The point before peak systole where the total flow levels off (the point right before it starts to rise quickly) corresponds to end diastole. Following peak systole, the total flow drops quickly until it levels off, which corresponds to end systole. Peak diastole is not typically a well-defined point so we place this temporal landmark at the point midway between end systole and end diastole.

Automatic Cardiac Output and Volumetric Measurements

Automatic measurement of cardiac output is done using the following method:

i) The relationship between the main DFT components of the velocity images, along with the already determined peak systole landmark (described elsewhere) are used to identify the main regions of arterial flow from the left and right ventricles.

ii) A variety of flow continuity filters is used, one after the other, to separate the arterial flow region into two pieces, aortic and pulmonic flow. The point in the initial arterial flow mask with the largest velocity provides a reliable point known to be in either the aorta or the pulmonary artery. Separation of the two regions of flow can be determined, for example, by examination of the size of the region within the resulting filter that can be flooded starting at the point of maximum flow. Once the first piece is identified, the second piece can be identified, for example, by flooding from the maximum flow point in the remaining regions.

iii) Once two regions have been identified one corresponding to aortic flow and one to pulmonic flow, the two regions can be allowed to grow back a limited amount (with individual pixels only being assigned to one mask or the other) and with the original arterial flow mask providing absolute limits to the amount of growth. Allowing at least a little dilation of the masks can also be very important as the preceding process operations may have put small holes in the resulting regions that would tend to hinder the next steps in the method.

iv) The two flow regions can be identified as aortic and pulmonic flow based on their spatial relationship to each other and their very different expected shape and orientation in space. Once this is done the original arterial flow mask is essentially divided into two regions, one labeled aortic flow and the other labeled pulmonic flow.

v) As the aorta is essentially one continuous pipe, the path of the aorta can be traced from a starting point within the artery until the two ends are reached. At each point the main peak systole flow direction can be determined by averaging over a small region around the point. Orthogonals to the flow direction can then be projected from the starting point at regular angular intervals to determine the boundary with the masked aortic region, thus determining an approximately circular contour around the starting point.

vi) Once a contour has been determined as a polygon on the plane orthogonal to the main flow direction for some starting point. The starting point is re-centered in the polygon. At this point a small step (for example, one millimeter) can be taken from the center point in the positive or negative flow direction, depending on which way from the starting point we are tracing, and the process then repeated. This is continued until we step out of the mask at each end.

vii) Once contours have been produced at regular intervals along the aorta, essentially producing a mesh, they are refined at each individual timepoint using either the anatomy images (possible if dealing with a blood flow enhanced dataset) or by using through velocity for the systole timepoints and interpolation between. One possible approach is to use a snake algorithm to accurately identify the desired boundary for each contour at each point in time.

viii) Once refined contours have been determined, the major and minor diameters of each contour are measured, the major diameter being the largest diameter and the minor diameter being the largest diameter orthogonal to the major diameter.

viii) The next task is to identify good contours in the main region of the ascending aorta between the aortic valve and the bifurcations that occur at the top of the aorta, as this is the region that needs to be used when measuring cardiac output. This can be done in a number of acts. First, ascending aorta regions are easily separated from descending regions by flow direction. The remaining contours can then be scored using a combination of the continuity and variability of the contour area and diameters (major and minor) both spatially (along the aorta) and temporally at one point in the aorta. Scores can be averaged along the aorta to look for regions of good scoring as opposed to simply identifying individual, highly scored, contours. Using this method, one can eliminate regions in the neighborhood of the bifurcations at the top of the aorta and also regions that might exist near the aortic valve and on into the left ventricle, as these regions, by their nature, will score badly.

ix) Once good regions of the ascending aorta have been identified, the highest scoring individual contours can be selected for the actual cardiac output measurement. If possible, measurement is done at multiple points along the ascending aorta, which improves the result through averaging along with providing automatic determination of the quality of the measurement by examining the variability (thereby, also providing estimates of the measurement uncertainty). In addition, examining the result of multiple measurements of the flow along the ascending aorta allows for a judgement on the quality of the velocity eddy-current-correction that is currently being applied.

x) Once the ideal contours have been selected along the ascending aorta, cardiac output is determined by the usual flow measurement techniques.

4-D Volumetric Measurement

In order to calculate the volume of a particular region, we have developed three options within the analytics service provider (ASP) system interface.

Option 1: Fixed Axis

Two points in 3-D space define the primary axis of a volume of interest.

A straight line connects these 2 points (i.e., fixed axis). The axis is then divided into discrete points (say 2-40 for example) that define the locations where a slice will be placed. Slices are aligned orthogonal to the axis such that they do not intersect. Slices do not have to be evenly spaced. An MPR is rendered at all slice locations to allow a user to see what the medical image looks like at that slice location. Then either manually or automatically a closed contour is created on every slice to define the boundary of the volume at that slice location. There could be multiple closed contours at every slice location. There could also be no contours at all on one or more slices. In the case of 4-D or higher dimensional studies (i.e., studies that show volume change, or said different, multiple frames per slice), there can be separate contours per frame. Once all contours have been placed for all frames and slices, a 3-D surface is created connecting the contours of all slices for a particular frame. The way the 3-D surface is created from a set of closed contours is explained above in “4-D Mesh Creation from Closed Contours”. If there is a 4-D or higher dimensional volume, a change in volume can be calculated by computing the volume of each frame and subtracting it with another frame. This is especially important when trying to quantify ventricular function which then gives stroke volumes and ejection fractions.

Option 2: Moving Straight Axis

This method is similar to Option 1, except that in the case of a 4-D volume, the landmarks or points that define the two endpoints of the axis can move over each frame (e.g., timepoint). This causes the volume to potentially move locations in 3-D space without changing volume.

Option 3: Fixed Curved Axis.

This method is similar to Option 1, except that the line connecting the 2 endpoints does not have to be straight. This line can be curved or have multiple straight and curved sections. This is handled in the system with a spline that connects points/locations between 2 endpoints. These points/locations can be anywhere and not necessarily always between the 2 endpoints.

Option 4: Moving Curved Axis

This method is similar to Option 2, except that in the case of a 4-D volume, the landmarks or points that define the two endpoints of the curved axis can move over each frame (e.g., timepoint). This causes the volume to potentially move locations in 3-D space without changing volume.

In all of the options above, there could be multiple axes. For example there could be a “Y” shaped axis that splits in 2 from 1. There is also the option of having both straight and curved axes that split and come together to create the volume. The point of this would be to account for more complex shapes that still have a primary axis (i.e., centerline).

In all of the options above, there is also the option of displaying how the 3-D volume intersects an MPR. The intersection must be a collection of one or more closed contours. These closed contours can be rendered on the MPR. In addition, these closed contours can be edited by moving the contour in the new (non orthogonal) view. The intersection contours can be computed both on the client as well as the server, or be adaptive depending on local resources. For cardiac imaging, common non-orthogonal views are 2, 3, and 4 chamber views. The contours can be edited in these views by only allowing the editing to be in a certain direction (i.e., along the slice plane).

Out of Plane Measurements and Tracking Mode

Measurements in a cardiac system from volumetric MRI data has several complexities. For example, the shape, position, orientation, and velocity of the valve plane can change significantly over a cardiac cycle. We solve this by using 2-D contours that move through 3-D space. Either manually or automatically, contours are placed at the border of the valve opening on the plane that is most perpendicular to flow direction. The position and orientation of the valve plane are tracked for each phase of the cardiac cycle. The evaluation of flow is performed through standard finite methods integration, however, in the event that the valve plane is moving the linear and angular velocity of the valve plane can be included in the flow computation for that phase. During visualization, when cycling through phases the position and orientation of the MPR can track with the valve plane. If a measurement is visualized when the current MPR is out of plane, the contour is rendered semi-transparent.

Segmentation Continuity Equation Driven Segmentation of Blood Pool

Once again, mass conservation (i.e., continuity) with the incompressibility assumption can be used to show that divergence must be zero everywhere in the blood pool. By computing the divergence everywhere, the system can define the extents of the blood pool by a threshold divergence value. The divergence outside the blood pool will be larger (i.e., air in the lungs) or the velocity will be low (i.e., velocity signal in static tissue), which both help in identifying the lumen boundary. The divergence map does not need to be the sole input into a segmentation algorithm, instead it could added to other inputs and weighted appropriately.

Automatic Landmark Detection

The typical ways to create an automatic landmark detection algorithm is look for certain shapes in images and measure distances and angles between these shapes. If the measurements lie within a certain band they are classified. Several other physiologic inputs can be added to the algorithm. For instance locating a volume of fluid that increases and decreases substantially with every heartbeat (this is likely to be a ventricle). Once a ventricle is found, the inlet and outlet of the valve can be found by following streamlines. Once a valve is found, it is easier to find the remaining valves because they are typically always a certain distance and angle away from each other.

The algorithm that is selected to find the landmarks can be of the machine learning type. Since the ASP (e.g., Arterys) will be constantly collecting data that has been validated with correct landmark placing by a clinician this data needs to be used as a training set (e.g., statistical aggregation of data). Every dataset that needs to be analyzed can be co-registered with an ‘atlas’ that is built with the training set data. Once a sufficient number of datasets are collected, additional input parameters such as type of disease (i.e., healthy, tetralogy of Fallot, etc.) can be used to bin the datasets prior to be analyzed. Every bin could have slightly different landmarks and measurements depending on the type of disease and what pathology is expected. If it is known that a dataset is a patient that has a single ventricle, the automatic landmark detection algorithm needs to adjust for this as it will never find 4 valves.

In particular the aortic and pulmonic valve landmarks can be determined using the following process:

i) Identify regions corresponding to arterial flow from the left and right ventricle. Filters have been developed (described elsewhere) that are able to do this with high reliability.

ii) Separate the region of arterial flow into two regions, one corresponding to the aorta and one to the pulmonary artery. This process is described in detail under cardiac output.

iii) Once one region corresponding to either flow from the left or right ventricle has been determined, the other region is determined by subtracting from the starting region corresponding to both flows. The regions can then be easily identified as left ventricle flow or right ventricle flow based on their physical dimensions and orientations in space (also described under cardiac output).

iv) Once the two regions of flow have been identified, initial approximations for the location of the aortic and pulmonic valve can be determined by carefully tracing the bulk flow back to its apparent origin.

v) Once reliable initial estimates are produced for the location of the two valves, other techniques can be used to refine the valve location. For example, one could examine the blood flow acceleration and intensity in the region surrounding the initial estimate in order to refine the location of the valves.

Interactive 4-D Volume Segmentation

Segmentation of ventricles from a cardiac scan is critical to determining ventricular function. Automatic ventricular function technique may involve:

-   -   an input of two or more points representing control points of a         spline;     -   the endpoints of the spline denote the apex of the ventricle and         the exit valve (pulmonic or aortic);     -   using these points generate MPRs with plane normals set to the         tangent of the curve at regular intervals along the spline         curve;     -   on each MPR apply an active contour model to find the boundary         (epicardium or endocardium) of the ventricle; and     -   generate a 3-D mesh using the points of each of these contours.

Active contour models are subject to instability from the forces that act on them. To reduce this instability, instead of simply generating the contours such that they are spaced at the desired output spacing (distance between contours), the system generates many contours spaced very tightly together. Also, if the input data has temporal data, contours at the same location are generated using data from adjacent time points. Contour shape and quality is then measured against typical contours from a ventricle. If a contour is deemed to be of sufficient quality it is included in generating a final result. The final results are generated by averaging the included contours that are close to the position and time along the input curve. With a mesh constructed at both end systole and end diastole the difference in volume represents cardiac output and ventricular function.

In one example implementation, the ASP system and software would provide single click 4-D volume segmentation. This would allow the user to click areas of interest (e.g., blood pool, myocardium, bone, etc.) while freely navigating (i.e., rotating, panning, zooming, slice scrolling, time scrolling) the 3-D volume. Since a full 3-D volume segmentation algorithm is challenging to construct and be accurate, a second option is to display 3 orthogonal views to the user while the user draws the boundary of the area the user would like to segment. For the heart, the view that is displayed can be a 2, 3, and 4 chamber view of the heart in addition to a short axis view. The user only needs to create 2 orthogonal contours in long axis, and then the software can automatically or autonomously create a 3-D surface based on interpolating the two contours. The 3-D surface can be shown in short axis to the user for quick modification. In addition to showing the anatomic images, the blood velocity images (with or without vectors) can be overlaid onto the anatomic images to further clarify where the blood pool boundary is during the interactive 3-D volume segmentation process.

Adaptive Flood Fill

The system makes use of multiple types of floods which may be distinguished as 2-D vs. 3-D, by connectivity used during the flood (6, 18, or 26 way connectivity), and radius constrained vs. a flood constrained by a maximum number of steps. In all cases, the flood works by moving outward from a specified seed point and including a pixel in the result of the flood if it is 1) connected to the rest of the flood (using whatever connectivity was specified), 2) has an intensity within a specified threshold of the pixel at the seed point, and 3) the pixel is within the specified radius of maximum number of steps of the seed point. The result of the flood is a two- or three-dimensional connected mask. The flood algorithm is used in solids in the form of a 3-D flood to mark static/non-static tissue, in volumes where a 2-D flood can be used to generate a contour in the short axis stack, and in flow quantification, where a 2-D flood may be used to flood a vessel to determine the flow contained within the flood.

To generate a contour from a radius-constrained 2-D flood, we make use of the fact that the flood will necessarily be connected and that it is a binary image. Because of these facts, we may apply a standard border tracing algorithm to come up with a contour which will ignore any holes that may be present within the interior of the flood.

From the generated contour, the next operation is to reduce the generated contour from potentially hundreds of points to a small set of control points to be used by a closed cubic spline to accurately approximate the actual contour. A naïve down sample where the system simply spaces a fixed number of control points spaced equally around the contour does not work as well as other approaches, as this approach frequently results in the loss of important features in the contour such as concave portion of the flood which was going around a papillary muscle. To get around this, a “smart” down sample approach is employed which proceeds in a number of acts. To begin with, each point in the contour is assigned a corner strength score ranging from −1 to 1, as well as assigning each point an area of “influence”. Once this is done, the contour is reduced to only those points where their corner strength is maximal within their area of influence. Additional criteria are also enforced in this stage, such as ensuring we have a minimal point spacing and ensuring our detected corners are sufficiently strong. The result of the preceding operation is a list of “corners” detected in the flood. By using these as control points in a spline, this approach ensures that the spline will not lose any interesting features in the contour. However, any long stretches of relatively low curvature in the original contour will not be detected as corners, which can result in significant portions of the resulting contour not having any control points, leading to a poor approximation by a spline in such segments. To get around this, an error metric is computed for each pair of control points by calculating the area of a closed contour formed by the segment of the original contour passing through the points, and the segment of a spline passing through those points. If the error is above some fixed tolerance, another control point is added at the midpoint of the segment of the original contour. This operation is repeated until each segment has a computed error below the required tolerance.

This flood-to-contour tool is can be used in at least two places in the application: for flooding slices of a ventricle while performing a volumetric segmentation, and in flow quantification. In the case of the flood for volumes, the returned contour is dilated by 8% in order to capture more of the ventricle as a raw flood fill often underestimates simply because of the difference in pixel intensities close to the heart wall. For a flow flood, the result is dilated by 12% because the flood tool works on anatomy, which means the undilated flood will often miss flow near the vessel wall.

Overall Process Automated Reports

In a way similar to how echocardiographic reports are generated, an automated report based on 4-D flow MR data can be created by allowing the user to click on the type of patient they have. The ASP (e.g., Arterys) will have unique report templates that are specific to a certain pathology or type of user (i.e., patient or clinician). All of the values, curves, images, and cine movies in this report can be automatically populated in the report template. Since landmarks are placed as part of the pre-processing step, all the important information can be automatically saved in the database and exported to this report.

Automated Integration Tests

A tool called node-webkit that is designed for making client side Web applications using node.js to perform automated integration tests. Although not designed for this purpose, it allows us to run both client and server software stack within the same environment allowing up complete control over the client and server applications at the same time. Using infrastructure mixed with a test tool called mocha, we write tests that emulate the customer interaction with the client while asserting both the client and server processing of that interaction along with the resulting state of the application. This method of integration testing is novel and superior to other tools that are mostly vision based, for this type of User Interface testing.

Hybrid Client Server Rendering

Description: Some workflows require one or multiple images to be rendered at the same time that have linked properties. In some cases the current workflow step may require simultaneous viewing of 20 images. If each of these images was retrieved with a distinct HTTPS request, performance would suffer greatly as there is significant overhead in creating and sending a request. Instead, we render all the images onto one large image, and only make a single HTTPS request for that ‘sprite sheet’. The client then displays the images by using pixel offsets. For example, if a view had four images each 256×256, the sprite sheet might be 256×1024 with each of the images stacked one on top of another. The client would then display 4 images at 256×256 by using offsets of 0, 256, 512, and 768.

In addition, any lines, markers, or planes in the images are drawn on the client as an overlay, and the information that informs the client how to render the overlay comes from the server via a JSON message. This provides higher quality rendering of the overlay data than if the overlay were to be rendered on the server and then encoded as a JPEG and transmitted.

Automated Global Endurance and Stress Testing

In order to perform load testing and endurance testing, we launch a multitude of client processes on a multitude of computers (which can be geographically distributed) to start specialized web browsers in which we have complete control over their execution environment. They are directed to the application and load the client as a normal browser would, then we directly interact with the client state controlling the software and making it behave as certain workload. The client and server metrics are recorded during load testing and run for longer periods of time for endurance testing.

Pusher Pushing Data from a Medical Device to Remote Servers

We have developed software to monitor for active studies, and push the results to our remote service in the cloud. A folder is monitored for files being generated by a scanner, and upon completion, all relevant data is bundled together and pushed via a secure connection using a unique secret and key per scanner for authorization to our remote cloud servers. Disk space (e.g., nontransitory storage media) usage is minimized by immediately deleting any intermediate files.

Upon a successful transfer, the data integrity of the transferred content is verified against the local content by reproducing the package process and comparing the output of a cryptographic hash function. Repeating the process like this ensures that any new data that may have been generated by a scan was not missed in the case of delays during the scanning process which may trigger premature transfer of the data to ASP's (e.g., Arterys) servers.

In the case of a failed transfer, due to server or network errors a configurable number of attempts will be made with an increasing interval of rest between each attempt, before the pusher assumes the transfer was a failure. However, after a failed transfer (including all subsequent attempts), the pusher will continue to monitor for incoming files, and will re-attempt another transfer at a later time.

Once data has been verified as successfully transferred, the data is removed by our software to conserve disk space on scanners.

A heartbeat message is sent from each pusher software running on every scanner providing the local log data and detailed status information of the scanner, providing continuous monitoring and increased response time to ensure scanner functionality during critical scan times.

During initial installation, a scanner will automatically register with the ASP (e.g., Arterys) by requesting a unique secret and key to sign all future requests with for authorization purposes. The scanner will be registered in our systems database, but not attached to any organizations. A technician is then able to attach all recently registered scanners to the correct organization through a web portal.

A pusher is able to auto update (if configured) by periodically requesting new versions from the ASP (e.g., Arterys.) If a new version is provided, it will install a new copy of itself, and restart. This allows for security and functionality updates to be deployed to scanners with no intervention from technicians. The heartbeat messages provide the information required to ensure success of this operation on the ASP's (e.g., Arterys) servers. The heartbeats enable us to determine any pushers that have not been updated recently, and reach out to hospitals directly to proactively ensure all software is up to date and secure.

FIGS. 3A-3B show an example process 300.

Puller—Archiving Artifacts

The puller software is used to archive generated artifacts at a hospital (for example PACS). It is installed within a hospital's network and registers itself automatically with the ASP (e.g., Arterys) using a similar method to the pushers. A request is made with some identifying information, and a secret and key pair is returned to sign future requests for authentication and authorization purposes. The puller is then attached to an organization by a technician through a web portal.

It is also possible to download a version for an organization directly, with a unique key and secret included automatically in the installation process, so there is no need to auto register and attach the puller once installed.

The configuration for artifact endpoints is done on ASP's (e.g., Arterys) servers. Multiple locations can be configured with hostnames, ports, AE titles, and any other required information the puller would need to transfer data to it. These endpoints can be named, and are selectable from the ASP's (e.g., Arterys) Web UI by a clinician when choosing where they would like their artifacts (reports/screenshots/videos) to be archived.

The puller monitors for artifacts by requesting a list from the ASP (e.g., Arterys) API at regular and frequent intervals. The list of artifacts includes a unique id, and all of the configuration information for the endpoint the artifact will be stored in. The unique ID is used as input into another API request to retrieve the artifact from the ASP's servers. The artifact is unzipped if required, and transferred using the configuration and method defined by the configuration included in the list request (e.g., storescp). Once all data is transferred, another API request using the provided ID is made to the ASP to mark the artifact as archived, and it will no longer appear in the list generated by the first request in the process loop. Once the artifact has been marked as archived, the ASP's servers will notify a user that archival is complete.

The puller sends heartbeat requests to the ASP's system providing detailed logs to help validate and ensure everything is functioning as expected. The puller will also occasionally—at a configurable time (e.g., once an hour or day)—make an API request to the ASP's servers for new versions of the puller software. If a new version is available, it will be downloaded, installed and the puller will restart itself.

Example request to retrieve a list of artifacts:

GET https://app.arterys.com/api/1/artifact?status=pending&timeout=20 [  { “id” : “55006362619baaad4323f799”, “name”: “report_one.zip”, “digest”: “f90sdaf9d0safd0safd09safd”, “size”: 3523234, “dicom_host”: “192.168.1.3“”, “dicom_port”: 1999, “dicom_aetitle”, “aetitle for dicom endpoint” },  { “id” : “454bf977be1cfbe146f36549”, “name”: “report_two.zip”, “digest”: “9320028003002930sass9safd”, “size”: 1221134, “dicom_host”: “192.168.1.3“”, “dicom_port”: 1999, “dicom_aetitle”, “aetitle for dicom endpoint” } ]

FIGS. 4A-4B show an example process 400 of monitoring for artifacts and archiving.

We have developed a method to securely deliver sensitive patient information to a client application from a service without disclosing the sensitive information to the service provider.

The data prior to being sent to the service provider is stripped of all patient identifiable health information, which is registered with the service and the original sensitive data is replaced with unique token identifier provided by the service.

The client when interacting with the service provider will identify these tokens and use an independent transport layer to replace the tokens with the sensitive patient health information.

Below is an example of a possible implementation of such a system:

Actors:

The user which interacts with the client software (user)

The client application (client)

The service which holds the sensitive patient information (service)

The application service provider

1. The user indicates to the software a set of files it would like to send to an application service provider.

2. For each file all sensitive information is gathered in JSON format and registered with the service over an http request.

Example

POST https://sensitive.arterys.com/register-data HTTP/1.0   {     “PatientName” : “Franklin\Benjamin”     “Birthdate” : “1706-01-17”   }   returns   Location: “/4217ad2b78fff7eb9129a58b474efb3e”

3. The sensitive data is replaced with placeholders such as #{PatientName} and then the data is uploaded along with the Location url returned from the service.

4. When the client loads the data from the application service provider, strings that contain these sensitive tokens cause the client application to request the data from the service provider (either individually or in bulk).

Example

GET https://sensitive.arterys.com/4217ad2b78fff7eb9129a58b474efb3e#Patient Name returns “Franklin\Benjamin”

5. The client substitutes the tokens with the sensitive information.

Note: For authorization, we could use a sso such as sam12.

Workspaces

Workspaces are a solution the issues of storing and sharing a subset of application state throughout medical software.

Workspaces contain the application state of a study including any analysis, and when loaded they restore application the previous state. Application state includes the subset of component state related to a particular concern such as study review including measurements and ECC correction values etc.

Workspaces can be loaded and updated constantly while the user interacts with the software. Users start with a private default workspace when loading a study for the first time, and when reloading the most recently used applicable workspace is loaded.

Users can publish a study to a group or more users, which can also serve as a trigger for report generation and external system notifications.

When opening a published workspace for the first time a private copy of the workspace is created with is also loaded on subsequent reloads. Published studies are immutable and can never be modified.

Machine Learning with Medical Imaging

With a cloud interface, it is now possible to aggregate statistics from multiple sources to come up with predictions using machine learning. These multiple sources can be the results generated by multiple people within an organization, or even multiple organizations scattered across the world. The statistics that can be aggregated can be medical imaging pixel data, medical imaging metadata (e.g., DICOM headers), and for example the electronic medical records of patients (EMRs). The learning can be applied at a user level, at an organization level, or even at a macro level (e.g., globally).

In the case of trying to automatically quantify (e.g., annotate, measure, segment) medical images, there can be two different categories of deep learning, machine learning or artificial intelligence: For the medical imaging application, supervised learning is more appropriate because there is not sufficient data to learn from. In order to learn as effectively as possible, the cloud user interface has been tailored to allow users to add labels to the data in a structured fashion. For example, in the case of cardiovascular imaging, a user can make several measurements and label the measurements as they wish. Instead of allowing a completely user defined field, there is the option for a user to select a label from a predefined list that the ASP provides. By doing this, we can add labels to the data in a structured and automated fashion. Labeled data acts as the training data set to feed into a machine learning algorithm (i.e., like a random forest or deep learning CNN or RNN) so that the algorithm can predict an outcome based on new unlabeled data. For example, one optional step in the user review process is for them to “publish” their workspace or state in a way that confirms that they are happy with the labels that they have added to the data. The “publish” mechanism can be an icon in the user interface that they click to “save”, or it can be the results that get sent to archive (for example to a hospital PACS server). There just needs to be a way to differentiate a user creating dummy measurements and annotations with true clinical measurements and annotations.

The benefit of a cloud interface is that every time a user makes any modification within the system interface to the suggestion provided, this modification then is saved and fed back into the machine learning labeled data. This creates a reinforcement learning loop that adds very valuable training data. The suggestions provided by the machine learning algorithm can be provided once when a user logs in or in real-time every time a user makes a modification during their session. For example, when a user identified a voxel in a medical image that is anatomy, all similar voxels can be identified in real-time in their session.

In the case of trying to predict the outcome of a particular treatment (and giving a resulting probability measure) or to predict which treatment choice is better suited for a particular patient, data from the EMR is critical. Having access to labeled medical device data (e.g., medical imaging, genomic data, wearables) is not sufficient in determining best treatment decisions. This data needs to be aggregated across all retrospective cases to offer a prediction to a new patient that has similar medical device data.

Machine learning can also be used for search in medical images. A user can type in a search field and find all images that for example has a particular type of disorder. A user can then verify that all the studies presented to them have this disorder and this data can then be fed back into the training dataset.

Picture and Video Service

We want the user to be able to capture pictures and video of the current state of their workflow. These images and videos need to include both image data generated on our server and overlays rendered on the client browser. To accomplish this we have a node-webkit based video service that allows us to run both our client and server software stack within the same environment. We then restore the current state of the user's workspace on the node-webkit environment and leverage the same compute nodes that were allocated for that user's session. If a single picture is requested by the user the service simply takes a screenshot of the restored workspace and the resulting image file is returned. In the case of a video request the service takes a screenshot for each frame of the current workflow and compiles the screenshot images into a video file using a video encoder which is then returned. The returned images or video can be stored on the server or sent back to the client to be viewed.

Below is an example of a detailed software design for the picture and video service:

Screenshots and Video Capture ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Requirements {circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )} * screenshot should be a rendering of what the user currently sees in the viewport area * video can be an mpr cycled through time * video can be generated from a collection of key frames with in- betweens interpolating parameters that can be interpolated * video can be user interaction recording * output should contain everything that is on the viewport (image, webgl overlays, css overlays, ...) * screenshots and video frames should be full-quality Design {circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )} Since we render everything on the client we need a client to generate the image. Unfortunately, uploading a video would be prohibitive in the majority of network situations. Hence, a screenshot/video service will run in the cluster that uses client rendering technology. It will expose an interface over http to provide functionality defined in the requirements. The service spins up node webkit processes on demand to render videos and screenshots as requests come in. Upon receiving a request to render an image or collection of images, the service will launch a node webkit process and redirect it to signed URL for the user's worklist. The node-webkit process will then load the study and inject the user's workspace Next each frame will be rendered at full quality. As a frame is rendered, node-webkit will perform an X11 screen capture and crop to the canvas viewport. The image will be saved to disk. Once all frames have been captured the service will return the screenshot, or in the case of a video, a video will be encoded and returned. Data Flow {circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )} * user initiates request for screenshot or video. * webserver receives request * node-webkit process is started * node-webkit process opens a session, authenticated to load the required study * requested study is loaded * workspace in the request is injected into the study * upon completion of workspace load (including long running tasks like streamlines) it begins to render key frames * every frame is rendered full quality with no debounced image commands * as an image is rendered X11 screen grab (xwd) is executed on the window * the image is cropped to the viewport and saved to disk * if a video was requested encoding will run once images are generated * upon completion of all images an http response is sent back with the .png or .mp4 * upon webserver receipt of the result, it will be saved in S3 and a reference saved to the database Additional Tools and Optimizations {circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )} * node-webkit requires webgl so the service will need to run on G2 instances * program ‘xwd’ in ‘x11-apps’ can capture window * ImageMagick ‘convert’ can convert xwd to png * ffmpeg can be used to generate .mp4 from a collection of .png Details {circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )}{circumflex over ( )} Screenshots +++++++++++ Client message: ---- ws.emit(‘generate-screenshot’, params); ---- params: ---- {  workspace_id : ‘workspace-id’,  id : ‘app-id’,  study_id : ‘study-id’,  upload_id : ‘upload-id’,  window_width : ‘browser_window_width’,  window_height : ‘browser_window_height’,  hostname : window.location.hostname,  port : window.location.port,  pathname : ‘/app/xxx’ } ---- Video +++++ Client message: ---- ws.emit(‘generate-screenshot’, params); ---- params: ---- {  // same as screenshot plus  render_frames : [   {    orientation : [1,0,0,0,1,0,0,0,1],    position : [0,0,0],    timepoint : 1   ...   },   {    orientation : [0,1,0,1,0,0,0,0,1],    position : [0,0,0],    timepoint : 2    ...   }   ...  ],  betweens : optional_number_of_frames_to_interpolate_between_frames } ---- Web server handler +++++++++++++++++      The message handler for ‘generate-screenshot’ attaches the current workspace to the args being sent to the webkit services      The webkit-client module is then used to send a request to one of the webkit services.      Once the response is received a record is inserted into the database and the image or video is stored. Webkit-Client +++++++++++++      The webkit-client module is responsible for routing a screenshot request to a node that can handle it.      The webkit-client subscribes to redis messages that are published by the currently running webkit nodes.      These messages include the existing instances of node-webkit that are running with the app-id they are running with.      When a request is received the webkit-client attempts to find a node that already has node-webkit running with the requested app-id.      Alternatively if a session has not been created yet it chooses the node with the least number of running sessions.      Once the node has been identified it sends the message over HTTPS to that host.      Arguments are sent in the body as JSON in a POST to the route ‘/webkit/execute’.      When the result returns a callback is invoked with the binary and a JSON blob containing the type (image/png or video/mp4), along with other useful information collected (e.g., timing information, size) ---- function execute(args, cb) {   https.request(‘POST’,‘/webkit/execute’,JSON.stringify(args), function(res) {     cb(null, {       binary : res,       json : { type : headers[‘content-type’], info: { generation_start_time: <date>, generation_end_time: <data>}}     }) ;   }) ; } ---- Webkit-Service ++++++++++++++      The webkit-service is a micro service that exposes an HTTPS interface to generate screenshots and videos.      The webkit-service listens only for POST requests at ‘/webkit/execute’.      Upon receiving a POST to ‘/webkit/execute’ it creates a webkit-context and enqueues a request for a screenshot or video.      This module also takes care of authorizing the request that will be sent from node-webkit to the webserver by appending an auth_token associated with the special ‘webkit-screenshot’ user. Webkit-Context ++++++++++++++      The webkit-context module is responsible for managing the node-webkit process that will run to generate a screenshot or video.      Upon creation a webkit-context creates a working directory to store intermediate results.      Next, it configures node-webkit by copying a simple ‘index.html’ and ‘package.json’ file into the working directory, and the ‘args.json’ containing the arguments passed into the context to render the screenshot/video.      Then node-webkit is started, and runs through the process of generating a screenshot.      When node-webkit exits, the webkit-context will look for the appropriate screenshot or video file to respond with.      Only one screenshot per app-id can run at a time.      A webkit-context registers itself in redis so that a webserver can route screenshot and video requests. Node-Main +++++++++      The node-main module is the bridge module running in node-webkit.      When node-webkit starts it waits until the ‘global.window’ variable is defined, and then reads in the args.json file and starts executing the steps to generate a screenshot.      These arguments denote the width × height to make the window and where to redirect window.location.href to.      It assumes the redirect points to a web site that will set global.window.io, which is an ASP defined variable denoting the websocket connection.      Once the websocket connection has been made it invokes a ‘load-study’ command, and waits for ‘load-workspace-complete’.      Once all commands that may have been invoked by restoring a workspace are finished node-main starts capturing images.      If ‘args.json’ contained the field ‘render_frames’ it iterates through each one generating an image.      The images are generated by invoking xwd to dump the Xwindow.      ImageMagick convert is then used to convert to a png and crop to the ‘.ar-content-body-canvases’.      If there was more than one image generated then ffmpeg is invoked to encode the collection of images into an h.264 encoded video.      When the screenshot or video has been created, node-webkit will exit cleanly.      Any error will cause node-webkit to exit with a non zero code, which will indicate to the webkit-context that the screenshot has failed.

PHI Service

FIG. 5 shows a networked environment for a medical analytics system or platform 500, according to one illustrated embodiment. The platform comprises an analytics service provider (ASP) network 502 which comprises an ASP system 504 (e.g., one or more processor-based devices) which communicates through a firewall 506 with various systems associated with medical provider (e.g., hospital) networks 508 (one shown). The ASP system 504 provides some or all of the various functionality discussed above. For example, the ASP system 504 may be similar or identical to the image processing and analysis system 104 of FIG. 1, for example. The ASP system 504 may be implemented using a cloud architecture and, as such, may comprise a number of distributed processor-based devices. The ASP system 504 may access external systems via one or more communications networks accessible via the firewall 506, for example.

The medical provider or hospital network 508 may include one or more protected health information (PHI) systems 510 (one shown) operatively coupled to one or more external networks (e.g., Internet) via a firewall 518. The medical provider network 508 may also include a Security Assertion Markup Language (SAML) service 512 operatively coupled to the PHI service 510. In at least some of the implementations discussed herein, the SAML service 512 may be considered to be part of or integrated with the PHI system or service 510.

The PHI system 510 may be operatively coupled to an MRI acquisition system 514 which includes an MRI machine 515 (FIG. 7) and a host computer system 517 (FIG. 7). The PHI system 510 may also be communicatively coupled to a database 524 or other nontransitory processor-readable storage medium which stores medical study data received from the MRI acquisition system, among other data. The medical study data may include MRI data, 4-D flow data, or any other type of data which may have PHI or other protected or personal information. As shown in FIG. 8, the PHI system 510 may be communicatively coupled to a picture archiving and communication system (PACS) 525 or other destination storage associated with the medical provider.

The MRI acquisition system 514 is typically located at a clinical facility, for instance a hospital or dedicated medical imaging center. The MRI acquisition system 514 may be similar or identical to the MRI acquisition system 102 of FIG. 1. Various techniques and structures, as explained herein, may advantageously allow the ASP system 504 to be remotely located from the MRI acquisition system 514. The ASP system 504 may, for example, be located in another building, city, state, province or even country.

The ASP system 504 may include one or more servers to handle incoming requests and responses, and one or more rendering or image processing and analysis computers. The server(s) may, for example take the form of one or more server computers, workstation computers, supercomputers, or personal computers, executing server software or instructions. The one or more rendering or image processing and analysis computers may take the form of one or more computers, workstation computers, supercomputers, or personal computers, executing image processing and/or analysis software or instructions. The one or more rendering or image processing and analysis computers will typically employ one, and preferably multiple, graphical processing units (GPUs) or GPU cores.

While FIG. 5 illustrates a representative networked environment, typical networked environments may include many additional MRI acquisition systems, ASP systems, PHI systems, computer systems, and/or entities. The concepts taught herein may be employed in a similar fashion with more populated networked environments than that illustrated. For example, a single ASP entity may provide image processing and analysis services to multiple diagnostic entities. One or more of the diagnostic entities may operate two or more MRI acquisition systems. For example, a large hospital or dedicated medical imaging center may operate two, three or even more MRI acquisition systems at a single facility.

Generally, the PHI system 510 may create a secure endpoint for medical study data (e.g., DICOM files). The PHI system 510 may automatically or autonomously strip files of PHI, and upload the de-identified medical study data to the ASP system 504 for processing and/or analysis. Further, as discussed below, a web application may be provided for a user operating a client processor-based device 520 which has secure access to the medical provider network 508 (e.g., via VPN). The web application operates to merge local PHI data from the PHI system 510 with the de-identified data from the ASP system 504, without providing any PHI data to the ASP system.

An organization (e.g., hospital, other medical provider) may implement the PHI system 510 onsite or in the cloud. The PHI system 510 which implements the PHI service allows PHI data to stay within the medical provider's network and control, while allowing the ASP system 504 to function in the cloud while meeting regulatory laws and ensuring patient privacy.

As shown in the process 600 of FIG. 6, when a user loads a medical study (e.g., MRI) using a web browser executing on the client processor-based device 520 which has secure access to the medical provider's network 508, medical study data is re-identified on demand within the web browser. Data is requested by the web application from both the ASP system 504 (e.g., via a web application of the ASP system) and a web API of the PHI system 510 simultaneously. The PHI data and de-identified data are then merged seamlessly within the user's web browser executing on the client processor-based device 520 during an active session.

The PHI system 510 may provide an API for a medical device (e.g., MRI acquisition system 514) to transfer medical study data over an encrypted connection. The data may then be uploaded securely in an efficient method to the ASP system 504. This provides both ease of integration with current medical devices, and provides security for data transferred outside of a medical provider's network 508. The PHI system 510 may reduce complicated, per device network configuration by ensuring that all communication inside and outside the medical provider's network 508 is done securely (e.g., over an HTTPs protocol over HTTPs ports).

As discussed further below, artifacts, such as secondary capture objects and reports generated within the web application of the ASP system 504, may need to be pushed back to the medical provider's reporting system and/or PACS. The PHI system 510 acts as a secure proxy, pulling the artifacts from the ASP system 504 and pushing the re-identified data to the configured location within the medical provider's network 508. This allows the medical provider to use the services provided by the ASP system 504 without allowing any inbound network requests, which keeps the medical provider's network secure.

The PHI system 510 may also be self-updating, and may allow security updates as well as functionality updates without requiring intervention by staff of the medical provider.

FIG. 7 shows an example process 700 of operating the PHI system 510 to strip PHI data from DICOM files. The PHI system 510 receives the DICOM files, which include PHI data and pixel data, from the host computer system 517 of the MRI acquisition system 514. The PHI system 510 strips the PHI data from the DICOM files and stores the PHI data in the database 524. The PHI system 510 uploads the de-identified pixel data to the ASP system 504 via the firewall 518 for use by the ASP system 504 to perform the various functions discussed above.

FIG. 8 shows an example process 800 of storing a user generated report on the registered PACS server 525 associated with the medical provider. As shown, the user operating the client processor-based device 520 may request, via the web application, that the ASP system 504 create a report. Responsive to the request, the ASP system 504 generates the report. The PHI service 510 may from time-to-time poll the ASP system 504 for de-identified reports. When the ASP system 504 has one or more de-identified reports available, the ASP system 504 sends the one or more de-identified reports to the PHI system 510 via an encrypted transfer. The PHI system 510 then stores the received report to the PACS server 525 for later use.

FIG. 9 is a schematic diagram 900 of the PHI system 510, showing how DICOM files received by the host computer system 517 of the MRI acquisition system 514 are handled by the PHI system 510. Among other services, the PHI service 510 may include a scanner upload service 902, a de-identifier service 904, an uploader service 906, a PHI storage service 908, and a status aggregator service 910. Each of these services is discussed further below.

Generally, the scanner upload service 902 is responsible for uploading DICOM files from the host computer system 517 of the MRI acquisition system 514. The scanner upload service 902 also posts status of DICOM file processing to the status aggregator service 910. The scanner upload service 902 also sends extracted DICOM files to the de-identifier service 904.

As discussed further below with reference to FIG. 12, the de-identifier service 904 functions to strip or remove any PHI data from the DICOM files. The de-identifier service 904 then sends the de-identified DICOM files to the uploader service 906 and sends the stripped PHI data to the PHI storage service 908, which stores the PHI data in the database 524. The de-identifier service 904 also posts de-identification status information to the status aggregator service 910. The uploader service 906 sends the de-identified DICOM files to the ASP system 504 over an encrypted transfer protocol for processing by the ASP system.

FIG. 10 is a schematic diagram 1000 of the PHI system 510, showing how PHI service dependencies are organized. The PHI system 510 includes a base operating system (e.g., Ubuntu/SL7) which comprises bash scripts 1004, Docker 1006, and native executables 1008. The Docker 1006 includes a number of Docker containers which are used to implement the various microservices 1002 of the PHI system 510. As shown in FIGS. 9 and 11, such microservices 1002 may include the scanner upload service 902, the de-identifier service 904, the uploader service 906, the storage service 908, the status aggregator service 910, an SSL proxy service 1106, an artifact service 1108, and a launch service 1110, for example.

FIGS. 11A-11B (collectively, FIG. 11) are a system sequence diagram 1100 illustrating a launch sequence of the PHI service 510. The components associated with implementing the launch sequence include a service control node 1102, a key management service 1104 of the PHI service 510, the ASP system 504, the scanner upload service 902, the de-identifier service 904, the storage service 908, the SSL proxy service 1106, the artifact service 1108, and the launch service 1110.

At 1112 and 1114, the service control 1102 creates a signed request to the ASP system 504 via the storage service 908. At 1116, the ASP system 504 requests a plaintext data key from the key management service 1104. At 1118, the key management service 1104 returns the key to the ASP system 504 which, at 1120, returns the plaintext data key and an encrypted data key to the storage service 908 of the PHI system 510. At 1122 storage service 908 provides an indication to the service control 1102 that the storage service 908 has started.

At 1124, the service control 1102 sends a start command to the launch service 1110. At 1126-1130, the launch service 1110 requests a plaintext key from the key management service 1104 via the ASP system 504. At 1134, the launch service 1110 generates a volume key if none exists. The volume key is then encrypted with the plaintext data key and is now referred to as the encrypted volume key. The encrypted volume key is stored along with the encrypted data key. The encrypted data key uniquely identifies the plaintext data key, which allows the PHI system 510 to roll keys on subsequent launches. At 1136, the launch service 1110 notifies the service control 1102 that the launch service has started.

In at least some implementations, the volume key is used to initialize a mounted volume (e.g., Docker volume) as an EncFS file system in paranoia mode using aes-256-gcm. All other services which need to write data to disk need to first request the volume key from the launch service 1110. As the volume key may not be kept in memory, upon request, the launch service 1110 decrypts the encrypted volume key with the in-memory plaintext data key and returns the volume key to the requesting service. The requesting service then uses that volume key to mount the shared EncFS volume in decrypted fashion.

At 1138, the service control 1102 starts the de-identification service 904. At 1140, the de-identification service 904 gets the volume key from the launch service 1110 which, at 1142, returns the volume key to the de-identification service. At 1144, the de-identification service 904 uses the volume key to mount a shared EncFS volume. At 1146, the de-identification service 904 notifies the service control 1102 that the de-identification service has started.

At 1148, service control 1102 starts the scanner upload service 902. At 1150, the scanner upload service 902 gets the volume key from the launch service 1110 which, at 1152, returns the volume key to the scanner upload service. At 1154, the scanner upload service 902 uses the volume key to mount the EncFS volume. At 1156, the scanner upload service 902 notifies the service control 1102 that the scanner upload service has started.

At 1158, the service control 1102 starts the artifact service 1108. At 1160, the artifact service 1108 gets the volume key from the launch service 1110 which, at 1162, returns the volume key to the artifact service. At 1164, the artifact service 1108 uses the volume key to mount the EncFS volume. At 1166, the artifact service 1108 notifies the service control 1102 that the artifact service has started.

At 1168, the service control 1102 starts the SSL proxy service 1106. The SSL proxy service 1106 is the last to start. The SSL proxy service 1106 controls external access to all internal services. At 1170, the SSL proxy service 1106 notifies the service control 1102 that the SSL proxy service has started.

FIG. 12 is a flow diagram illustrating a process 1200 for the de-identification service 904 of the PHI service. The de-identification service 904 is responsible for processing a study uploaded by the scanner upload service 902, collecting all information, and ensuring that it is safe to upload to the ASP system 504. A primary component of the de-identification service 904 is the actual de-identification act performed on the DICOM data. In at least some implementations, a modified gdcmanon utility from the GDCM project may be used.

The process 1200 begins at 1202, for example, when the scanner upload service 902 sends extracted DICOM files for a study to the de-identification service 904. At 1204, a PHI processing module is initiated. At 1206, a number of processing acts 1208-1222 are performed. In particular, at 1208 a folder which contains the study to be processed is renamed. At 1210, all non-study files (e.g., shalsum) are removed. At 1212, the de-identification service 904 extracts PHI from the DICOM files. At 1214, the de-identification service de-identifies the DICOM files. All extracted PHI data may be collected and stored for every DICOM file and may be sent to the storage service 908 at the end of the process, for example.

At 1216, the de-identification service 904 extracts obfuscated UIDs. The de-identification act 1214 replaces a StudyInstanceUID with an obfuscated value. The original data is linked with the study sent to the ASP system 504 by this value.

At 1218, the de-identification service 904 performs a collision check for the obfuscated UID to ensure there is a unique mapping between the StudyInstanceUID and the obfuscated UID. If there is a collision, a different obfuscated UID may be generated to ensure a unique mapping between the StudyInstanceUID and the obfuscated UID.

At 1220, the de-identification service 904 sends the PHI data to the storage service 909, which stores the PHI data 1220 in the database 524, for example. At 1222, the de-identification service 904 moves the folder to the de-identified state. At 1224, once the processing act 1206 is completed, the de-identified data is queued for uploading to the ASP system 504 by the uploader service 906. At 1226, the process 1200 ends until, for example, another study is found which needs to be processed. At 1228, a PHI error processing module may be executed if an error is detected at any of the processing acts 1208-1222.

The PHI data collected may be organized in a document with two levels information, a study level and a series level. The data may be indexed by an obfuscated StudyInstanceUID which provides the link with the data stored by the ASP system 504. The PHI data may be sent to the storage service 908, which encrypts and stores the data in the database 524.

To handle ISO2022 data, the dcmconv utility (from the dcmtk project) may be used. Before reading PHI data from the reduced set of DICOM files, the DICOM files may be converted to UTF-8. This speeds up the process by limiting the number of files that need to be converted, while ensuring all PHI data collected is in a consistent format.

The utility gdcmanon handles de-identification in a folder of DICOM data. However the project only de-identifies to the 2008 NEMA standard. As such, in at least some implementations a modified version of the gdcmanon utility is used which adds the required DICOM tags to be compliant with the latest DICOM standard.

The utility also encrypts the PHI and stores the PHI within each DICOM file as a new tag. The PHI system 510 does not send any de-identified data, even when encrypted, so the utility is further modified to skip the step of inserting a new tag of encrypted data. This further speeds up the process by removing the need to add an additional step of removing that tag later.

For the PHI system 510 to function, only a small subset of PHI at the study and series level as needed. However, the DICOM standard removes many more fields. To keep the database 524 of the PHI system 510 smaller, which enhances performance for the user, the PHI system may only store the required data in the database 524. In cases where additional fields are needed, or if there is a need to reprocess the PHI data, the de-identified data removed from each DICOM file may be stored (e.g., as a JSON file which is compressed and archived).

FIGS. 13A-13B (collectively, FIG. 13) are a flow diagram illustrating a process 1300 for the uploader or pusher service 906 of the PHI system 510. The pusher service 906 has two main tasks. The first task is to transfer the identified studies to the ASP system 504. The second task is to monitor the status of an uploaded study, and update the internal status of the PHI system 510 until an end state is reached. This allows the host computer system 517 to request the status for a study from the PHI system 510, and to receive information from the ASP system 504.

At 1302, the pusher service 906 monitors a folder for de-identified studies provided by the de-identification service 904. The pusher service 906 then begins an upload file process 1304. At 1306, the pusher service 906 bundles the de-identified data (e.g., tar and gzip the study). At 1308 the pusher service 906 calculates the shalsum of the new bundled file (e.g., tar file), which shalsum is used to verify the integrity of upload and also provides a key with which to request status updates. At 1310, the pusher service 906 may rename the file (e.g., “<shalsum>.tgz”) to ensure the file name contains no PHI.

At 1312, the renamed file may then be uploaded to the ASP system 504 using a send retry loop 1314. The sender retry loop continues to attempt to upload the file with an increasing delay between attempts. If the file fails to upload after a number of attempts, an error uploading module 1316 may be executed. If the upload is successful, the shalsum is verified to ensure data integrity. At 1318, the uploaded file is then queued for processing by the ASP system 504.

At 1320, the uploader service 906 may remotely monitor the status of the uploaded file. As an example, the upload or service 906 may use the shalsum as a lookup key. Possible states for the uploaded file may include “error processing,” which signifies an error occurred, “processing,” which signifies that the file is being processed, or “processed,” which signifies that the file has been processed.

The storage service 908 is responsible for storing extracted PHI data so it can later be retrieved for re-identification. When the storage service is run the storage service communicates with the ASP system 504 and retrieves the plaintext data key and encrypted data key, as discussed above. These keys are then stored in memory. Any data the storage service 908 writes to disk is encrypted with the plaintext data key and is stored alongside the encrypted data key which identifies the plaintext data key that was used to encrypt the data.

FIGS. 14A-14B (collectively, FIG. 14) are a system sequence diagram 1400 illustrating a process 1400 for re-identification of the data in a web browser executing a web application on the client processor-based device 520 (FIG. 5). At 1402, the web browser sends a request to the ASP system 504 to load an application. At 1404 the ASP system 504 loads the application on the web browser. A user who has successfully been authenticated on the web application of the ASP system 504 may be given a web token (e.g., JSON Web Token). As discussed above, this web token is sent to the PHI system 510, by the web browser, when requesting data. The SSL proxy service 1106 (FIG. 11) forwards all data requests to an authorization service of the PHI system 510 to ensure that the user still has valid, authenticated access to the web application. This is a transparent process as far as the user is concerned.

At 1406, the web browser requests information about the PHI system 510 from the ASP system 504. At 1408, the ASP system 504 sends the PHI system information to the web browser. At 1410, the web browser requests a PHI access token from the ASP system 504. PHI access tokens are encrypted and can only be read by the ASP system 504. At 1412, the ASP system 504 sends the encrypted PHI access token to the web browser.

At 1414, the web browser queries the PHI system 510 for a worklist of available studies. All requests to the PHI system 510 contain the encrypted PHI access token. At 1416, the PHI system 510 sends encrypted access token to the ASP system 504 for validation. The ASP system 504 confirms that the access token is valid (i.e., the access token belongs to an active session). At 1418, the ASP system 504 sends a notification to the PHI system 510 indicating that the access token is valid.

After appropriate authentication/authorization, the PHI system 510 retrieves the worklist and study PHI data via an API of the storage service 908. At 1420, the PHI system 510 sends the worklist and PHI data to the web browser.

At 1422, upon selection of a study from the worklist, the web browser sends a request to the ASP system 504 to load a study. Responsive to such a request, the ASP system starts loading the study onto a computing system (e.g., a compute cluster). At 1424, the web browser sends a request to the PHI system 510 for PHI data associated with the selected study. The granted access may be cached for a short time and, as such, this request may not require validation. At 1426, the PHI system 510 sends the PHI data for the selected study to the web browser. At 1428, once the study is loaded on the compute cluster, the ASP system 504 sends the study data to the web browser 520.

At 1430, the web browser merges the study data received from the ASP system 504 with the PHI data received from the PHI system 510 and presents the same to the user for use of the services provided by the ASP. Thus, using the process 1400, the user has access to the full study data and analytics provided by the ASP system 504 without providing the ASP system with any access to PHI data.

FIGS. 15A-15B (collectively, FIG. 15) are a system sequence diagram illustrating a process 1500 for implementing the artifact re-identification service 1108. The artifact re-identification service 1108 is responsible for contacting the ASP system 504, downloading any pending artifacts, re-identifying the downloaded artifacts, and storing them to a medical provider destination system, such as the PACS 525, a web-based radiology information system (WRIS), etc.

At 1502, the artifact re-identification service 1108 sends a request to the ASP system 504 requesting a list of pending artifacts. At 1504, the ASP system 504 provides the artifact rei-identification service 1108 with a list of pending artifacts.

At 1506, the artifact re-identification service 1108 sends a request to the ASP system 504 to get one of the pending artifacts in the received list of pending artifacts. Artifacts may be secondary capture objects, reports, or anything else that the ASP system 508 may want to push to the medical provider destination storage 525. At 1508, the ASP system 504 sends the requested artifact to the artifact re-identification service 1108.

At 1512, the artifact service 1108 requests PHI data for the artifact from the storage service 908. This request may utilize the obfuscated StudyInstanceUID tag, as supplied in the response, to query the storage service 908 for the original, associated tag information for that StudyInstanceUID. At 1514, the storage service 908 of the PHI system 510 sends the PHI data to the artifact service 1108.

At 1516, the artifact service 1108 re-identifies the artifact. For example, for DICOM data, the dcmodify utility may be used to rewrite the DICOM tags for the artifact to match those that were originally stored.

Upon successful re-identification, the artifact pushed to the medical provider destination storage 525. The destination may be a PACS, WRIS, or any other supported endpoint. Connection details may be provided from the ASP system 504 with the artifact details.

At 1522, the artifact service 1108 sends a notification to the ASP system 504 indicating that the artifact re-identification process for that artifact is completed. At 1524, the ASP system 504 notifies the artifact service 1104 that the status for that artifact has been updated, indicating that such artifact will no longer be returned in the list of pending artifacts during the next iteration.

The above described automated approaches remove the subjectivity in identifying anatomical structure and flow, which is endemic in conventional approaches, providing a high level or repeatability. This repeatability allows new uses for the MRI data. For example, MRI data for single patient may be reliably reviewed across different sessions for trends. Even more surprisingly, MRI data for a plurality of patients may be reliably reviewed for trends across a population or demographic.

FIG. 16 a schematic illustration of a Trusted Broker Service (TBS) system 1601 integrated with the PHI service pipeline shown in FIG. 5, according to one illustrated embodiment. The TBS system 1601 allows an authorized third party to control access to data that has been uploaded to the analytics service provider (ASP) network 502 from an authorized uploader. In one example embodiment, the client processor-based device 520 may be that of the authorized third party. In other embodiments, the PHI system or service 510 may be that of the authorized third party. Although the TBS system may be applied to and used to store and control access to medical study data, which may include MRI data, 4-D flow data, or any other type of data which may have PHI or other protected or personal information, in other embodiments, the TBS and PHI systems described herein may be applied to and used to store and control access to various types of medical and non-medical data, including, but not limited to, one or more of: sensitive data, confidential data, classified data, secret data, proprietary data, personal information, genetic information, medical history data, disease-related data, mental health data, laboratory test results data, blood test results data, uranalysis data, drug test results data, genetic test results data, biopsy data, electrocardiogram data, x-ray imaging data, medical scan data, CT scan data, ultrasound scan data, medical imaging data, exploratory surgery data, criminal background data, personal background data, military record data, sealed court record data, disciplinary record data, academic record data, data subject to a nondisclosure agreement, genealogical data, birth record data, personal credit data, personal financial data, privately held company data, trade secret data, data subject to a secrecy order, scientific data, oil and gas exploration data, geologic exploration data, geological data about new oil finds, geographical data, data regarding areas of potential discovery of oil, and data regarding areas of potential discovery of valuable minerals.

The ASP network 502 comprises an ASP system 504 (e.g., one or more processor-based devices) which communicates through a firewall 506 with various systems associated with medical provider (e.g., hospital) networks 508 (one shown) and with the TBS system 1601. The ASP system 504 provides some or all of the various functionality discussed herein regarding the ASP network 502. The ASP system 504 may be implemented using a cloud architecture and, as such, may comprise a number of distributed processor-based devices. The ASP system 504 may access external systems, such as the TBS system 1601 via one or more communications networks accessible via the firewall 506, for example.

In one example embodiment, there may be three major components in this communication path: 1. Uploader, 2. ASP system 504, 3. Trusted Broker Service 1601. In one example embodiment, the authorized Uploader may be, be part of, or integrated with the PHI system or service 510 described above. The TBS system 1601 may include one or more computers or other data processing systems, for example, a computer such as that shown in FIG. 2, that stores data and computer-executable instructions and executes the computer-executable instructions accordingly to perform the processes described herein.

The Trusted Broker Service accepts JSON metadata (e.g., metadata regarding medical study data) from the Uploader (e.g., the PHI system or service 510), and assigns it a unique identifier and returns that identifier to the Uploader. Internal to the Trusted Broker Service 1601 the identifier is associated with instructions indicating how to store and download the data under access control.

The Trusted Broker Service 1601 exposes an application programming interface (API) which returns the access instructions, when given a unique identifier. The authorized third party (e.g., represented by the client processor-based device 520) may remove the unique identifier (and associated records) from the Trusted Broker Service 1601 thereby rendering data uploaded with that unique identifier inaccessible.

The Trusted Broker Service 1601 receives communication from both Uploader and the ASP system 504. This communication may take place using Transport Layer Security (TLS). Components are given a self-renewing Domain Validated SSL Certificate. This allows the calling component to be assured that outgoing communication occurs only with an authentic called component. The Trusted Broker Service 1601 uses client cert verification to verify incoming connections from the ASP system 504.

In one example implementation, there are three certificates required by the Trusted Broker Service 1601:

private_key

-   -   The private key associated with the public_cert

public_cert

-   -   A domain-validated public cert chain in pem format, signed by a         trusted CA which the Trusted Broker Service uses as its public         cert

arterys_ca_cert

-   -   A certificate authority in pem format, used for client         certificate verification on incoming requests from ASP system         504         The above certificates may be retrieved from the ASP system 504         during startup.

In an example embodiment, the certificates have an expiry period and are automatically renewed before expiry.

In an example embodiment, the Trusted Broker Service 1601 makes a periodic request for updated certificates from the ASP system 504, via an API request.

If updated certificates are present, the Trusted Broker Service installs them.

Encryption Based Control:

In an example embodiment, the Trusted Broker Service 1601 generates encryption information for each metadata upload. This includes an encryption/decryption algorithm to use, along with a unique encryption key.

Whenever ASP system 504 would like to save or read data associated with the upload identifier, ASP system 504 uses the upload identifier to request the encryption information from the Trusted Broker Service 1601.

The authorized third party may remove the unique identifier (and associated records) from the Trusted Broker Service 1601 thereby rendering data uploaded with that unique identifier impossible to decrypt.

FIG. 17 is a schematic illustration of the Uploader, and the TBS system showing how encryption based data uploads are performed by the TBS system, according to one illustrated embodiment.

In order to communicate with the Trusted Broker Service the Uploader must first request the Trusted Broker Service address, and an authentication token from the ASP system. (1)

Authentication of this request is done using an API Key and Secret present on the Uploader component during install.

Upon successful receipt of the address and authentication token, the Uploader sends the metadata it wishes to store, along with authentication token to the Trusted Broker Service. (2)

The Trusted Broker Service makes an outgoing connection to the ASP system requesting verification of the authentication token. (3)

On successful verification, the Trusted Broker Service saves the metadata sent by the Uploader. This involves the generation of a unique identifier for that metadata, along with some encryption information indicating how the ASP system should encrypted future associated data. The unique identifier is returned to the Uploader. (4)

The Uploader now sends the data to the ASP system, along with the unique identifier. (5)

The ASP system requests the encryption information for the data from the Trusted Broker Service, by querying it with the unique identifier. (6)

The returned encryption information is used to encrypt the uploaded data prior to storage. (7)

FIG. 18 a schematic illustration of an end user system, ASP system and the TBS system showing how encryption based data downloads are performed by the TBS system, according to one illustrated embodiment.

When the ASP system receives a data request it looks up the corresponding upload identifier in internal storage (1). For example, this request may be from the client processor-based device 520 shown in FIGS. 5 and 16. In other embodiments, this request may be from the PHI system or service 510 shown in FIGS. 5 and 16.

A request for the encryption information associated with that upload identifier is sent to the Trusted Broker Service (2).

The returned encryption information is used to decrypt the requested data from storage before it is returned (3).

Revocation of Data Access:

The Trusted Broker Service allows searching of its upload metadata in order to locate the data whose access is to be revoked.

Once the matching records are located, they may be removed from internal storage. Subsequent requests for encryption information given their unique identifier, will no longer find a match and no encryption information will be returned.

This ensures that ASP system will not be able to decrypt any stored data, thus revoking access to that data.

FIG. 19 a schematic illustration of the Uploader, ASP system and the TBS system showing how access based data uploads are performed by the TBS system, according to one illustrated embodiment.

Access Based Control:

The Trusted Broker Service generates a pre-signed, time-expiring access URL allowing ASP system to store a file to, or download a file from that URL, depending on access policy associated with the URL.

In order to communicate with the Trusted Broker Service the Uploader must first request the Trusted Broker Service address, and an authentication token from the ASP system. (1) Authentication of this request is done using an API Key and Secret present on the Uploader component during install.

Upon successful receipt of the address and authentication token. the Uploader sends the metadata it wishes to store, along with authentication token to the Trusted Broker Service. (2)

The Trusted Broker Service makes an outgoing connection to the ASP system requesting verification of the authentication token. (3)

On successful verification, the Trusted Broker Service saves the metadata sent by the Uploader. This involves the generation of a unique identifier for that metadata. The unique identifier is returned to the Uploader. (4)

The Uploader now sends the data to the ASP system, along with the unique identifier. (5)

ASP system requests a pre-signed upload URL, by sending a file name and the unique identifier to the Trusted Broker Service. (6)

The Trusted Broker Service associates the requested file name to the unique identifier and generates a pre-signed upload URL for that file name. The Trusted Broker Service returns the URL to the ASP system. (7)

The ASP system sends the data it wishes to upload to the pre-signed upload URL. (8)

FIG. 20 a schematic illustration of an end user system, ASP system and the TBS system showing how access based data downloads are performed by the TBS system, according to one illustrated embodiment.

When ASP system receives a data request the ASP system looks up the corresponding upload identifier, and file name in internal storage (1).

A request for a pre-signed download URL associated with that file name and upload identifier is sent to the Trusted Broker Service (2).

The Trusted Broker Service generates a pre-signed download URL for the requested file (3).

ASP system can then request data at the location specified by the pre-signed download URL (4).

Revocation of Data Access

The Trusted Broker Service allows searching of its upload metadata in order to locate the data whose access is to be revoked.

Once the matching records are located, they may be removed from internal storage. Subsequent requests for a pre-signed url fail as no match will be found.

This ensures that ASP system will not be able to access any stored data controlled by the Trusted Broker Service.

Some of all of the access based data uploading, data access and access revocation processes may be used instead or in conjunction with the encryption based data uploading, data access and access revocation processes described herein.

FIG. 21 is a flow diagram illustrating a process 2100 of operating an analytics service provider (ASP) system of a medical analytics platform, according to one illustrated embodiment. For example, the analytics service provider (ASP) system may be the ASP system 504.

At 2102, the ASP system receives medical study data along with a unique identifier of the medical study data.

At 2104, the ASP system stores the unique identifier of the medical study data on the ASP system.

At 2106, the ASP system sends a request for access instructions for the received medical study data, wherein the request includes the unique identifier of the medical study data.

At 2108, the ASP system receives the access instructions in response to the request.

At 2108, the ASP system stores the medical study data on the ASP system using the received access instructions.

FIG. 22 is a flow diagram illustrating a process 2200 of operating a trusted broker service (TBS) system of a medical analytics platform, according to one illustrated embodiment.

At 2202, the TBS system receives a request from an analytics service provider (ASP) system for access instructions for medical study data to be stored on the ASP system, wherein the request includes a unique identifier of the medical study data.

At 2204, the TBS system retrieves access instructions for the medical study data using the unique identifier.

At 2206, the TBS system sends the access instructions for the medical study data to the ASP system in response to the request for the access instructions.

FIG. 23 is a flow diagram illustrating a process 2300 of operating a medical study data uploader (MSDU) system of a medical analytics platform, according to one illustrated embodiment.

At 2302, the MSDU system sends a request to an analytics service provider (ASP) system for an authentication token and an address of a trusted broker service (TBS) system, the request including an application programming interface (API) key and unique secret stored on the MSDU system.

At 2304, the MSDU system receives from the ASP system the authentication token and the address of the TBS system in response to the request sent to the ASP system.

At 2306, the MSDU system sends metadata regarding medical study data along with the authentication token to the TBS system using the address of the TBS system.

At 2308, the MSDU system receives from the TBS system a unique identifier of the medical study data in response to the sending of the metadata regarding medical study data along with the authentication token to the TBS system.

At 2310, the MSDU system sends to the ASP system the unique identifier of the medical study data along with the medical study data for storage on the ASP system.

FIG. 24 is a flow diagram illustrating a process 2400 of operating a medical analytics platform including a medical study data uploader (MSDU) system, an analytics service provider (ASP) system and a trusted broker service (TBS) system, according to one illustrated embodiment.

At 2402, the MSDU system sends metadata regarding medical study data to the TBS system.

At 2404, the TBS system generates a unique identifier of the medical study data.

At 2406, the TBS system generates access information for the medical study data.

At 2408, the TBS system associates the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data.

At 2410, the TBS system stores on the TBS system the metadata regarding the medical study data.

At 2412, the TBS system stores on the TBS system the association of the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data.

At 2414, the TBS system sends the unique identifier of the medical study data to the MSDU system.

At 2416, the MSDU system sends to the ASP system the unique identifier of the medical study data along with the medical study data for storage on the ASP system.

At 2418, the ASP system stores the unique identifier of the medical study data on the ASP system.

At 2420, the ASP system sends a request for access instructions for the received medical study data, wherein the request includes the unique identifier of the medical study data.

At 2422, the ASP system receives the access instructions in response to the request.

At 2424, the ASP system stores the medical study data on the ASP system using the received access instructions.

Supplemental Data Retrieval

A typical DICOM viewer may have direct access to a picture archiving and communication system (PACS). The DICOM viewer may be able to query for a list of studies, and can retrieve image data as required to display the image data for a physician. It is possible to send studies to other applications from the PACS directly. This is a manual process, and adds a great deal of latency when sending to applications outside of the hospital's infrastructure (e.g., to a cloud application). A cloud application needs to be able to load the studies without a direct connection to the PACS, and when configured, must be able to retrieve the studies beforehand to be accessible immediately when required to fully process a study. Typically a cloud based viewer also requires all data needing to be rendered to be sent to the cloud. Sometimes, it is not desirable for some scan data to be sent to the cloud. For example, secondary captures which may include pixel data containing PHI. However, it is still desirable to view that data within the same viewer being used to process the rest of the scan.

In at least some implementations, the PHI service, discussed above, that is hosted within the organization performing the scan, may store a cryptographic hash that can be used to identify related scans. Scans can be related in any way, but typically will be done at the patient level. When a study is uploaded to a cloud application, if similar studies for the same patient are required, the cloud application can generate a RETRIEVE request. The PHI Service queries the cloud application for generated RETRIEVE requests. When a request is made, the PHI service parses the information which includes the related hash to search for, along with filter parameters and host information for the location of the data (e.g., the organization's PACS). Filter parameters include date ranges, any other DICOM tag (e.g., Modality), etc.

The PHI service, using the location information and filter information, makes a QUERY request, getting a list of all matching data. If the location does not support all filters in its query language, the PHI service may then do further filtering of the data. For example, if it is not possible to filter data based on a specified tag from the PACS location, then the PHI service may retrieve all meta data, and do further filtering on the results before retrieving the actual scan data.

The scan data may be retrieved by the PHI service, and processed the same way as a scan manually sent to the PHI service.

The PHI service may also provide an API to directly perform the query and retrieve. When a browser is connected to the PHI service and authorized to view PHI data hosted on it, the cloud application web client has the ability to directly make a RETRIEVE request and get the list of possible scans from the PHI service directly, and also to make a RETRIEVE request that causes the PHI service to pull the specified scans based on the filters.

The PHI service may provide an API for the cloud application web client to monitor the progress of studies being retrieved.

The PHI service may provide an API such that a web browser connected on the organization's network, and authorized to view PHI, can make a request to retrieve a list of series from a remote location (e.g., a PACS) for a selected scan. The PHI service maintains a list of de-identified series already pushed to the cloud application. If there are additional series, that the cloud application web client is able to render directly (that is, it does not require the backend system of the cloud platform), then the web client can make a request for a specific series' pixel data. The PHI service may retrieve the series, extract the pixel data, and return it via the API request to the web client. The web client may then be able to render it without having direct contact with the remote storage service, and any pixel data which it is undesirable to send to a cloud application may be maintained within the organization's network and control.

FIG. 25 shows a networked environment for a medical analytics system or platform 2500, according to one illustrated embodiment. The platform 2500 may be similar or identical to the platform 500 of FIG. 5. The platform 2500 comprises the analytics service provider (ASP) network or remote service 502, which is communicatively coupled via a firewall to a PHI service 510 operated by a medical provider or hospital network 508 (FIG. 5). The PHI service 510 includes a query-retrieve or supplemental data service 2502, which is coupled to a data store 2506. A client application 2504 may be coupled to the supplemental data service 2502 and the remote service 502, as discussed above.

FIG. 26 shows a method 2600 of operating the query-retrieve service 2502, according to at least one embodiment. The query-retrieve service 2502 may be hosted within an organization (e.g., hospital). This service 2502 can process a request for supplemental data. The request may contain fields to filter by, including date ranges, and DICOM tags such as modality. The request may also contain a related hash which is used to find related studies from de-identified data.

The request may also contain an action indicating what to do with the results of the request. The action may be to Query Only, Process, or Render the data.

At 2604, the query-retrieve service processes a supplemental data request 2602 by first doing any lookups in its internal storage (e.g., data store 2506 of FIG. 25) to determine the correct PHI and tags to use if a related_hash is provided as a query field. The related_hash is the combination of multiple PHI tags, and may need to be converted into the real values before a query can be made.

The processing request may contain the required connection information to query the remote data store. The query-retrieve service may perform a query using the data store's API (such as DICOM query (C-FIND)). At 2606, the results are filtered as required if the data store's API does not fully support the filtering that the query-service supports. For example, if it is needed to filter by StudyDate and StudyTime combined, the service may be able to only filter on one or the other as they are separate tags, so the extra filtering may happen once the query-service is processing the results.

Once the results of the query are filtered, the query-service may then perform the required action on each result. At 2608, the query-service determines if the action is Query Only. If the action is Query Only, at 2610 the resulting information may be returned. This is useful for providing supplemental worklist data without retrieving any image data until requested manually. If the action is not Query Only, at 2612 the query-service may fetch medical data.

At 2614, the query-service determines whether the action is Process or Render. At 2616, if the action is Process, the query-service gets the image data from the remote store, for example a DICOM Get (C-GET). The data may be pushed through the PHI server through the typical pipeline when receiving a scan from a Modality. The data may be de-identified, the PHI may be stored, and the de-identified pixel data may be pushed to the cloud.

If the action is Render, at 2618 the query-service gets the image data from the remote store (e.g., C-GET) and extracts the image data. At 2620, the image data may be returned, but no PHI or pixel data may be retained on the PHI server except for temporary caching. Advantageously, this allows a web application to retrieve image data and render it without having it pushed to the cloud.

The query-service may accept processing requests through a web based API accessible through an authorized client. The query-service may also periodically query the cloud for any generated processing requests. A processing request generated by cloud servers may be used to retrieve scans for longitudinal tracking and analysis purposes. A request through the web browser may be used to provide supplemental worklist data to allow a clinician to manually trigger the retrieval of an important scan to be pushed to the cloud application, or to retrieve image data not present in the study processed in the cloud, so that reports and secondary captures that may contain burned in PHI can be rendered without requiring data be pushed beyond the organization's (e.g., hospital) secure network.

Worklist Enrichment

Maintaining PHI within an organization's network produces a unique challenge when integrating with a cloud application when displaying a list of available scans. When the two sources each contain partial data, creating a complete list of merged data can be done on the client displaying the data. However, it is inefficient to do this as the number of scans grows, and a web browser becomes unable to quickly search, sort and organize the data, instead of using common techniques of database querying and paging to provide efficient and correct responses.

To efficiently query and display worklist data when a large number of scans exist, it must be possible to search and filter the list of scans based on a number of criteria. When the data is split between the cloud application and a PHI service, as discussed above, merging and sorting requires the web client to pass data between services and to have access to enough information to accurately sort and display the data correctly. With a growing database of scans, the amount of data being sent through the web client to the different services grows and becomes too cumbersome. User and organization specific data may also be stored per worklist entry such as tags, bookmarks, new/viewed state, and other identifiers unique to one source of data such as processing times and upload dates.

A possible solution to this problem is to synchronize the data from the cloud source to a service located within the organization. Using a long polling mechanism, a worklist-sync service, also referred to herein as a worklist-enrichment service, queries the cloud server, waiting for updates. When an update to the worklist occurs, the worklist-sync service receives the changes, and immediately reconnects. In this way, when a change occurs, such as a user bookmarking an entry, or loading a scan changing its state from new to viewed, the data is updated in real-time on the PHI service (whether the web client is connected or not).

Any change made to the worklist is recorded in a database with a modified date. When the worklist-sync service connects, it provides the date of its last synchronization. All items from the database that were modified after the last synchronization date are returned to the worklist-sync service. The worklist-sync service then reconnects with the new last synchronization date.

If no modifications have been made since the last synchronization date, the worklist-sync service may maintain an open connection with the cloud server. When a new record is written to the database on the cloud server, an event may notify the open connection of an update, and the worklist-sync service may immediately download and synchronize the new data.

This approach allows the web client to retrieve its worklist from a single source. If connected to the service hosted within the organization, the web client is able to query and retrieve data from the worklist hosted on the service. If unable to connect to the service within the organization, the web client is able to fallback and query and retrieve the worklist from the cloud server, which maintains the same information with the PHI removed.

FIG. 27 shows a networked environment for a medical analytics system or platform 2700, according to one illustrated embodiment. FIG. 28 shows a sequence diagram for operation of the platform 2700. The platform 2700 may be similar or identical to the platforms 500 and 2500 of FIGS. 5 and 25, respectively. The platform 2700 comprises the analytics service provider (ASP) network or remote service 502, which is communicatively coupled via a firewall to the PHI service 510 operated by a medical provider or hospital network 508 (FIG. 5). The PHI service 510 includes a worklist-sync service 2702, also referred to as a worklist-enrichment service, which is coupled to a data store 2706 of the PHI service. A client application 2704 may be coupled to the worklist-enrichment service 2702 and the remote service 502, as discussed above. As shown in FIG. 28, the remote service 502 may include an application server 2802 and a processing server 2804, for example.

The worklist-enrichment service may be hosted within an organization (e.g., hospital). The worklist-enrichment service retrieves updated worklist information from the cloud server by using a long polling technique.

A connection is made to a cloud API with a date indicating the last synchronization time in the request. If any updates to worklist data are available, the cloud API immediately returns the results. If no updates are available, the worklist-enrichment service maintains an open connection with the cloud API. When a connection is completed (e.g., either with returned results, or closed due to timeouts), a new connection is immediately made.

When the cloud API returns results, the additional worklist updates are applied to the PHI server's internal database, and the last synchronization time is updated for the new request.

Worklist data may be enriched at the organization level or the user level. Tags may be applied to a scan that are available to all users of the organization. However, a new or viewed state, and bookmarks may be specific to a given user. Because of this, the worklist-enrichment service maintains a database of the scans, and additional information for each scan at both the organization level and the user level. As new users are added to the cloud system, the worklist-enrichment service automatically adds that user's data to create personalized worklists.

The worklist-enrichment service provides a web API allowing an authorized web client to search, filter, and retrieve data based on all collected information. The web API is used to retrieve data only. Updates to worklist data are done through the cloud servers, and updated in real-time through the long polling mentioned above. This allows the web application to function even when no connection is possible to the PHI server. If no connection is possible, the worklist may be served by the cloud server (excluding PHI), but all updates made to the worklist may be automatically kept in sync on the PHI server through the server-to-server connection discussed above.

Additional scans uploaded directly to the cloud may be added as new entries through the worklist-enrichment service, allowing the PHI server to be a single source of data when the web application is connected.

The various embodiments described above can be combined to provide further embodiments. To the extent that they are not inconsistent with the specific teachings and definitions herein, all of the U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in the Application Data Sheet, including but not limited to U.S. Provisional Patent Application No. 61/571,908, filed Jul. 7, 2011; International Patent Application No. PCT/US2012/045575, filed Jul. 5, 2012; U.S. Provisional Patent Application No. 61/928,702, filed Jan. 17, 2014; International Patent Application No. PCT/US2015/011851, filed Jan. 16, 2015; U.S. patent application Ser. No. 15/112,130 filed Jul. 15, 2016; U.S. Provisional Patent Application No. 62/260,565, filed Nov. 29, 2015; U.S. Provisional Patent Application No. 62/415,203 filed Oct. 31, 2016; U.S. Provisional Patent Application No. 62/415,666 filed Nov. 1, 2016; and U.S. Provisional Patent Application No. 62/501,613 filed May 4, 2017; are incorporated herein by reference, in their entirety. Aspects of the embodiments can be modified, if necessary, to employ systems, circuits and concepts of the various patents, applications and publications to provide yet further embodiments.

These and other changes can be made to the embodiments in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited by the disclosure. 

1. A method of operating a medical analytics platform, the medical analytics platform including an analytics service provider (ASP) system, the method comprising: receiving, by at least one processor of the ASP system, medical study data along with a unique identifier of the medical study data; storing, by at least one processor of the ASP system, the unique identifier of the medical study data on the ASP system; sending, by at least one processor of the ASP system, a request for access instructions for the received medical study data, wherein the request includes the unique identifier of the medical study data; receiving, by at least one processor of the ASP system, the access instructions in response to the request; and storing, by at least one processor of the ASP system, the medical study data on the ASP system using the received access instructions.
 2. The method of claim 1 wherein the access instructions include encryption information for encrypting the medical study data and wherein the storing the medical study data includes encrypting the medical study data for storage using the encryption information.
 3. The method of claim 1 wherein the access instructions include a pre-signed, time-expiring access uniform resource locator (URL) and wherein the storing the medical study data includes storing the medical study data to the pre-signed, time-expiring access URL according to an access policy associated with the pre-signed, time-expiring access URL.
 4. The method of claim 1 further comprising: receiving, by at least one processor of the ASP system, a request from a client processor-based device for the medical study data stored on the ASP system; retrieving, by at least one processor of the ASP system, the identifier of the medical study data from storage on the ASP system in response to receiving the request for the medical study data stored on the ASP system; sending, by at least one processor of the ASP system, a request for access instructions for the medical study data stored on the ASP system, wherein the request for access instructions includes the unique identifier of the medical study data; receiving, by at least one processor of the ASP system, the access instructions in response to the request for the access instructions; accessing, by at least one processor of the ASP system, the medical study data stored on the ASP system using the received access instructions; and sending, by at least one processor of the ASP system, the accessed medical study data stored on the ASP system to the client processor-based device in response to the request received from the client processor-based device.
 5. The method of claim 4 wherein the access instructions include decryption information for decrypting the medical study data and wherein the accessing the medical study data includes decrypting the medical study data using the decryption information.
 6. The method of claim 4 further comprising: retrieving from storage on the ASP system, by at least one processor of the ASP system, a file name associated with the medical study data stored on the ASP system in response to receiving the request for the medical study data stored on the ASP system, wherein the access instructions include a pre-signed download uniform resource locator (URL) and wherein the accessing the medical study data includes requesting, by at least one processor of the ASP system, the medical study data at a location specified by the pre-signed download uniform URL.
 7. The method of claim 1 wherein the medical study data is received along with the unique identifier of the medical study data from a medical study data uploader (MSDU) system, the request for access instructions for the received medical study data is sent to a trusted broker service (TBS) system, and the access instructions are received from the TBS system in response to the request.
 8. The method of claim 7 further comprising: before the receiving the medical study data along with the unique identifier of the medical study data: receiving, by at least one processor of the ASP system, a request from the MSDU system for an authentication token and an address of the trusted broker service (TBS) system, the request including an application programming interface (API) key and unique secret stored on the MSDU system; authenticating, by at least one processor of the ASP system, the request from the MSDU system using the application programming interface (API) key and the unique secret; sending, by at least one processor of the ASP system, the authentication token and the address of the TBS system to the MSDU system based on authentication of the request from the MSDU system; receiving, by at least one processor of the ASP system, a request from the TBS system for verification of the authentication token; verifying, by at least one processor of the ASP system, the authentication token in response to the request for verification from the TBS system; and sending, by at least one processor of the ASP system, verification of the authentication token to the TBS system.
 9. The method of claim 7 wherein the MSDU system is part of a protected health information (PHI) system.
 10. The method of claim 9 wherein the medical study data is de-identified medical study data that is de-identified by the PHI system.
 11. A method of operating a medical analytics platform, the medical analytics platform including a trusted broker service (TBS) system, the method comprising: receiving, by at least one processor of the TBS system, a request from an analytics service provider (ASP) system for access instructions for medical study data to be stored on the ASP system, wherein the request includes a unique identifier of the medical study data; retrieving, by at least one processor of the TBS system, access instructions for the medical study data using the unique identifier; and sending, by at least one processor of the TBS system, the access instructions for the medical study data to the ASP system in response to the request for the access instructions.
 12. The method of claim 11 wherein the access instructions include encryption information for encrypting the medical study data by the ASP system for storage on the ASP system.
 13. The method of claim 11 wherein the access instructions include a pre-signed, time-expiring access uniform resource locator (URL) to which the medical study data is to be stored by the ASP system.
 14. The method of claim 11 further comprising: before the receiving the request from the ASP system for access instructions for the medical study data: receiving, by at least one processor of the TBS system, metadata regarding the medical study data along with an authentication token from medical study data uploader (MSDU) system; sending, by at least one processor of the TBS system, a request to the ASP system for verification of the authentication token; receiving, by at least one processor of the TBS system, verification of the authentication token from the ASP system in response to the request for verification of the authentication token; and in response to the verification of the authentication token: generating, by at least one processor of the TBS system, the unique identifier of the medical study data; generating, by at least one processor of the TBS system, the access information for the medical study data; associating, by at least one processor of the TBS system, the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; storing on the TBS system, by at least one processor of the TBS system, the metadata regarding the medical study data; storing on the TBS system, by at least one processor of the TBS system, the association of the unique identifier of the medical study data with the access information for the medical study data and the metadata regarding the medical study data; and sending, by at least one processor of the TBS system, the unique identifier of the medical study data to the MSDU system.
 15. The method of claim 14 wherein the MSDU system is part of a protected health information (PHI) system.
 16. The method of claim 15 wherein the medical study data is de-identified medical study data that is de-identified by the PHI system.
 17. The method of claim 14 further comprising: receiving, by at least one processor of the TBS system, a request to revoke access to the medical study data stored on the ASP system; locating, by at least one processor of the TBS system, metadata stored on the TBS system regarding the medical study data stored on the ASP system for which access is to be revoked; removing from the TBS system, by at least one processor of the TBS system, one or more of: the metadata regarding the medical study data, the access information for the medical study data, and the unique identifier of the medical study data.
 18. The method of claim 17 wherein the request to revoke access to the medical study data stored on the ASP system is received from an authorized client processor-based device.
 19. The method of claim 17 wherein the request to revoke access to the medical study data stored on the ASP system is received from a PHI system.
 20. A method of operating a medical analytics platform, the medical analytics platform including a medical study data uploader (MSDU) system, the method comprising: sending, by at least one processor of the MSDU system, a request to an analytics service provider (ASP) system for an authentication token and an address of a trusted broker service (TBS) system, the request including an application programming interface (API) key and unique secret stored on the MSDU system; receiving from the ASP system, by at least one processor of the MSDU system, the authentication token and the address of the TBS system in response to the request sent to the ASP system; sending, by at least one processor of the MSDU system, metadata regarding medical study data along with the authentication token to the TBS system using the address of the TBS system; receiving from the TBS system, by at least one processor of the MSDU system, a unique identifier of the medical study data in response to the sending of the metadata regarding medical study data along with the authentication token to the TBS system; and sending to the ASP system, by at least one processor of the MSDU system, the unique identifier of the medical study data along with the medical study data for storage on the ASP system. 21-56. (canceled) 